Professional Documents
Culture Documents
This documents all UNIX, Oracle, SAP related errors that are worth sharing across teams.
TABLE OF CONTENTS
UNIX 2
ORACLE 4
SAP GENERAL 9
SAP PRESENTATION 15
SAP BACKUPS 19
SAP SECURITY 25
UNIX
Check
/oracle/<sid>/background/alert_<s
id>.log for alert log file.
TEMPORARY FIX
If tablespace is urgently getting
filled up, can increase size of
an oracle datafile on line
without rebouncing. “Alter
database datafile
‘<datafilename>’ resize
<new size>”
>saplicense -temp
to install a temp license
SAP GUI
Delete
/usr/sap/L71/DVEBGMS
00/data/SP*
Clean up stats file via st03
Clean up work process
trace files via sm50
Recycle spooler
Note: In order to get a better idea of the reason for the failure the following 3 steps are
highly recommended
1. Look into the logs and search for the instance of the first occurrence of any error
message instead of looking at the tail of the logs. Very little information is conveyed
and hardly anything can be deduced by looking at the brbackup/brarchieve return
code mentioned at the end of the logs. Most of the following data is catering to the
first error message that comes up in the logs.
2. Note that it is the first error msg that really counts and all the errors that crop up after
that are usually a follow up of the first error.
3. Note that the /var/opt/ctma/ctm/sysout logs are lot more accurate and better
furnished in detail as compared to the logs we see at SAP GUI or even in the
/saparch or /sapbackup directories. So if you are not able to see the error in the
usual places look at the sysout logs. [Just go to the dir and do $ ll | grep [jobname
that failed] to see the logs.]
#./sapg900_cleanup_pool.sh +3
var/opt/saparch/prod
#./sapg900_cleanup_pool.sh +10
var/opt/saparch/dvlp
sesu - orasid
svrmgrl
connect internal;
select * from
V$BACKUP;
alter tablespace
<tablespacename> end
backup;
2. Fire script
/opt/nb/bin/backoff_backup.sh
<SID>
./removelock.sh SID
7. Specified schedule The parmecs file would have Work with UIT to make
does not exist in the been refreshed to the incorrect sure correct parmecs file
specified class parameters gets refreshed.
Under /var/opt/ubkp/parmecs
change the schedule to w_8w_e
or whatever value was defined in
netbackup
Create user
OPS$ORA<SID> to
enable ‘ora<sid>’ to
perform normal
AIM COMMON ERRORS & SOLUTIONS Page 43 of 60
454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
9. ORA-00942: table or POSSIBLE CAUSES:
view does not exist 1) Auto-secure problem
BR303E Determination of 2) SAPDBA, CONNECT,
Oracle RDBMS version RESOURCE is not there for
failed OPS$<SID>ADM. To verify if
this is so,
svrmgrl
connect internal
select * from
dba_role_privs;
Check what roles have
been granted to
OPS$<SID>ADM
SOLUTION:
1) Ticket to UIT
2) Grant correct roles to OPS$
user:
svrmgrl
connect internal
grant sapdba to
OPS$<SID>ADM
grant connect to
OPS$<SID>ADM
AIM COMMON ERRORS & SOLUTIONS Page 44 of 60
454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
10. 903 job failure with This as due to insufficient
error: dbdump space. The backup was
successful in handling the
Internal error for sapdatas, but not the archives
/oracle/L01/saparch/L01arc since the dbdumps are all very
h1_54854.db… full. Alan Randall recommend to
add 2 35G dbdumps (dbdump11
and dbdump12).
# default:
$ORACLE_HOME/sapbackup
backup_root_dir =
(?/dbdump0,?/dbdump1,?/dbdum
p2,?/dbdump3,?/dbdump4,?/dbdu
mp5,?/dbdump6,?/dbdump7,?/db
dump8,?/dbdump9,?/dbdump10,?
/sapdata92,?/sapdata94,?/sapdat
a95,?/sapdata96)
/
var/opt/ubkp/scripts/ubkp049
_varopt_genfile.sh
generates the listings of files
to be backed up in /var/opt
directory
/
var/opt/ubkp/scripts/ubkp050
_varopt.sh <CLASS>
<SCHED> <HOST> <FILE>
backs up the files
/
var/opt/ubkp/scripts/ub
kp050_varopt.sh
sihp8040 d_2w_e
sihp8040 ubkp050_varopt
AIM COMMON ERRORS & SOLUTIONS Page 46 of 60
454382796.doc last saved 4/19/2012 04:38:00 PM
Following are the list of errors for which you should just forward the ticket to the resolution
owner:
[ Note: The Status code is the backint system status not brbackup/brachieve return code]
SOLUTION:
1) sesu - ora<sid>
2) cdexe
3) sqlplus internal
@sapdba_role <SID> UNIX
DIAGNOSIS:
1) more /etc/group | grep dba
2) If you see users other than
<ora>sid, request UIT to take
them out of DBA group
bdhm:/var/spool/sw/applications/
UBKP_SAPCTMA
UBKP_SAPCTMA
2) Monitoring scripts:
(thresh_ora.free,
thresh_ora.ext, thresh_ora.frag,
TableExtents.sql,
FreeSpace.sql,
TbleSpceFrag.sql)
bdhm:/var/opt/sapsoe_arch/depot
MONITOR
To know which :
1) Go to:
http://golx4001.na.pg.com/~
markj/pmdbs/
2) grep pmd /usr/seos/seos.ini'
will return several lines.
Look for the line that says,
"parent_pmd = ..." This will
identify the policy model.
char *ss_dba_grp[] =
{SS_DBA_GRP,
SS_OPER_GRP};