You are on page 1of 60

ERP COMMON ERRORS & SOLUTIONS

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

ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION


SUGGESTED SOLUTION
1. nfiles has reached 80% Number of simultaneous open This cannot be
files in UNIX. Need to reboot to prevented in 3.0F. Once
bring nfiles to zero. a file is opened, it is
never closed until
reboot.
2. SOE Refresh: when was SOE refresh / swinstall logs can
the last time files were be found in
refreshed into a host and /var/adm/sw/swagent.log
what files were
refreshed?

AIM COMMON ERRORS & SOLUTIONS Page 2 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
3. ethp2010: Disk If BIethp2010* are the biggest
utilization of files, ask Basis to run
/sapmnt/E4Q is 90% SAP_REORG_BATCHINPUT
housekeeping job with the correct
To find out which directory client variant.
is the biggest: ls -F |
grep “/” | xargs du The BI* files are batch input log
-s files that are generated whenever
there are batch input jobs
To find out which file inside running. These are cleaned up by
directory is biggest: BASIS job:
ls -l | sort -r -k5n SAP_REORG_BATCHINPUT

to find out which directory is This job contains a step which


the biggest under the same runs abap RSBDCREO which
mountpoint: du -x . reorganises the SBDC sessions
for a particular client. This clears
out any sessions that have been
fully processed and leaves the
ones that still have processing
requirements on them. The
current job in E4P was pointing to
client 098 instead of 420 so client
420 was not being cleaned up
AIM COMMON ERRORS & SOLUTIONS Page 3 of 60
454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
4. What is the IP of the Unix a) nslookup <SID> : Will use
server? DNS
b) /etc/rc.config.d/netconf
c) /etc/hosts
d) lanscan (get lan0); ifconfig
lan0
5. What do the svr* jobs a) svxrj001 job performs a
scheduled in EMEA database system check. Check
systems do? if database is up and running.
b) svxrj010 job performs a sapdba
-next. This checks if there are
no problems with the
max.extents.

6. Setting up a link in unix ln -s <source> <new file>


ln -s /var/opt/gsss/data/ANR
/var/opt/gsss/data/anr

The new file should not exist first.


7. MERCATOR_EXEL Remsh problem between bdhs
TCP/IP connection on and L6A for l6aadm. Make sure
L6A gets timeout error grace logins don’t expire and
remsh possible.

AIM COMMON ERRORS & SOLUTIONS Page 4 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
8. To see memory of glance \ F3
server
9. To see how many df - i or bdf - i
inodes a filesystem is
occupying

AIM COMMON ERRORS & SOLUTIONS Page 5 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ORACLE

ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION


SUGGESTED SOLUTION
1. DB error oerr ora <error #>

If error not found, it could imply


Oracle internal error. Ask user to
. contact Oracle for advice

Check
/oracle/<sid>/background/alert_<s
id>.log for alert log file.

AIM COMMON ERRORS & SOLUTIONS Page 6 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
2. Switch tablespace 1. sesu - orasid
from backup mode to 2. svrmgrl
normal mode 3. connect internal;
4. select * from V$BACKUP;
5. alter tablespace
<tablespacename> end backup;

Alternatively you can login goto


/opt/nb/bin and as root run
# ./backoff_backup.sh
This will automatically switch all
tablespaces to endbackup mode

AIM COMMON ERRORS & SOLUTIONS Page 7 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
3. Moving datafile without When the target and source is When the target and
stopping SAP different: source is same:
1. su - oraas1
1. Make a copy of the datafile 2. svrmgrl
from the source to the target. 3. SVRMGR> connect
internal
cp 4. SVRMGR> Alter
/oracle/SID/sapdata20/bta database
bi_1/btabi.data1 datafile
/oracle/SID/sapdata10/bta ‘/oracle/AS1/sap
bi_1/btabi.data1 data25/btabi_44/
btabi.data44’
Note: You will have to crate the offline;
directory [e.g btabi_1] on the 5. copy the file to some
target and change the file temp directory like
ownership to orasid:dba . Also ‘/oracle/sid/sapreorg’
once you have copied over the and ‘/var/adm/crash’
file, you will have to change the 6. mount the directory
ownership of the file itself [here ‘/oracle/AS1/sapdata2
btabi.data1] to orasid:dba. 5’ with correct
ownership
2. su - orasid 7. copy the file from
3. svrmgrl; connect temp directory to
internal mounted filesystem
AIM COMMON ERRORS & SOLUTIONS Page 8 of 60
454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
4. Create a large rollback
tablespace 1. svrmgrl; connect
internal
2. CREATE TABLESPACE
PSAPROLLBIG
DATAFILE
'/oracle/<SID>/sapdata<
#>/
rollbig_1/rollbig.data1
' SIZE 400M
DEFAULT STORAGE(INITIAL
64M NEXT 16M
pctincrease 0);

(The path '.../rollbig_1' must be


created first, if necessary)

5. Create a rollback CREATE ROLLBACK SEGMENT


segment PRS_BIG TABLESPACE
PSAPROLLBIG STORAGE
(INITIAL 64M NEXT 16M
MAXEXTENTS 300 OPTIMAL
512M);

AIM COMMON ERRORS & SOLUTIONS Page 9 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
6. Activate PRS_BIG and > alter rollback segment prs_1
deactivate the old offline;
rollback segments ...
> alter rollback segment prs_10
offline;
> alter rollback segment prs_big
online;

To make this permanent:


1. Insert the line
"rollback_segments=(PRS_BIG
)" in
init<SID>
2. Deactivate the line
"rollback_segments=(PRS_1,...
) with #
3. Restart the DB

AIM COMMON ERRORS & SOLUTIONS Page 10 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
7. Maximum number of The db_files parameter is there in
datafiles have been two places, one in init.ora file
reached for a particular (which is easy to change) and the
tablespace. Cannot add other in controlfile, which can be
more datafiles changed only by rebuilding the
controlfile.

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>”

PERMANENT FIX (Downtime


needed):
Need to change db_files
parameter in init<sid>.ora and
controlfile
1. Change db_files in
/oracle/<SID>/dbs/init<sid>.ora
to higher number and reboot
AIM COMMON ERRORS & SOLUTIONS Page 11 of 60
454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
8. ORA-12203 : Note 131561
TNS:unable to connect to
destination; Many work process tried to
connect to the listener at the
Work processes completed same time, but listener is not able
but unable to restart. They to process all requests. Modify
can be restarted manually listener.ora to contain parameter
without any problems QUEUESIZE=50 and restart
listener

AIM COMMON ERRORS & SOLUTIONS Page 12 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
9. ORA-03113 end-of-file When you use svrmgrl to
on communication even start the database.
channel Note that this generally
happens only on a new
system or a system were
unix/patches or oracle
upgrades have been applied.

There is no straight forward


solution to this and you have
to try the following to reach
the solution [hopefully]
The Type of causes you can
look for:

Wrong permissions for


oracle binaries:

/orac;le/<SID>/bin must have


(6751 or -rwsr-x--x).
ora<sid> must have dba
group

AIM COMMON ERRORS & SOLUTIONS Page 13 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION

AIM COMMON ERRORS & SOLUTIONS Page 14 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
SAP GENERAL

AIM COMMON ERRORS & SOLUTIONS Page 15 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
1. Slow response time Network communication team to System performance
check whether network is having data to be reviewed.
heavy traffic.
Get in touch with user
ST06 to check CPU and make the following
utilization. preparation prior to any
SM04 to check all users long running batch job:
logged on to the system.
1. Cleanup pooldisk
ST03-> performance DB- 2. Lower
>Time Profile to check /oracle/sid/saparch
system average response threshold so that DM
time, wait time etc. gets notified earlier.
ST03-> performance DB- 3. Lower
>Top Time to check for long- saparch_guard.cfg
running programs. threshold so that
saparch kicks in
SM21 to check system logs. earlier.
ST22 to check for shot
dumps. Use ‘Selection’ to
specify more detailed
information.

SM66 to check programs run


AIM COMMON ERRORS & SOLUTIONS Page 16 of 60
454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
2. saplicense >saplicense -show >saplicense -show
to see all licenses installed. to see all licenses
installed.
>saplicense -get
to get the license used. >saplicense -get
to get the license used.
>saplicense -install
to install new license. Must delete Check that the license
old license first before installing used has expiry date
new one. 31/12/9999

>saplicense -temp
to install a temp license

Each SAP system comes with a


30-day temp license. If a license
expires, we can just use the temp
license till the new license is
received from SAP.

To request for a new license, first


obtain the Installation Number of
the system.

AIM COMMON ERRORS & SOLUTIONS Page 17 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
3. pgsapinfo time out on This could mean that the server is If it happens often, we
connection to host down OR can look at increasing
False alarm as follows: the timeout value or
suppressing the page for
There are a lot of rfc connections a timeout error.
queued up on the server, which
prevents sapheart from logging in. Note:/momauto/manage
This is sometimes due to a large rs/evtmgt/bin/
download of master data or idocs sapheart/run.sh calls
from another server. Usually, pgsapinfo C program
users are not able to log in during
this period. The backload is
usually cleared in a few minutes.
4. st03 does not show Check to see if RSCOLL00
updated performance (collector for performance
data. monitor) is scheduled to run every
hour via sm37. If not, ask Basis
to schedule the job

AIM COMMON ERRORS & SOLUTIONS Page 18 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
5. st03 contain These servers do not do any
invalid/non-active servers harm. To clean them up, do the
that were carried over ff:
during DBCopy from st03 à Goto à Performance
source system Database à Contents of database
à Delete 1 server. Enter the

name of inactive server. This will


delete its data from the MONI
table.

AIM COMMON ERRORS & SOLUTIONS Page 19 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
6. Cannot ftp or ping 1. All UNIX boxes configured to
sapserv4 (204.79.199.2) access sapserv4/sapserv3
from any of Asia SAP [OSS/FTP] should be
servers specifically authorized by SAP
[at TCP/IP level not at
hostname level]. Normally one
would open a ticket with sap to
add a VALID UNIX box. Surely,
the SAP router bdhifddi can do
this.

Complete list of servers


registered in SAP: etsp0021,
bdhi, bdhifddi, bdhk, bdhy,
bhhc, blhd, blhp, sihp8008,
testframe.

Possible cause of problem: IP


has changed and SAP has not
been updated. Open message
to SAP to correct the problem

2. Try to do the ff:


"traceroute
AIM COMMON ERRORS & SOLUTIONS Page 20 of 60
454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
7. Note 108328 recommends setting
instance profile
DBIF_RSQL_NO_MEMO rsdp/rclu/cachelimit=0; and
RY error on table CDPOS setting R3trans and tp env
in ANR 4*0. There is a variable to
7.5MB cache limit RCLU_CACHELIMIT=0. Related
note 141465

8. SAP-FI See oracle instructions on how to


DBIF_RSQL_SQL_ERR do this:
OR in AS1 client 525
1. Offline small segments (i.e.
PRS_1 to PRS_9)
2. Created RBIG segment in
PSAPROLLBIG and online
RBIG in AS1

AIM COMMON ERRORS & SOLUTIONS Page 21 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
9. Stat file keeps on OSS 6833
growing even after
manual deletion 1) Set Max. number of records
per cumulated call to
10,000. Standard value (and
on almost all our other
systems) is 20,000 but this
seems to be too much
causing time outs.
2) stat/timeout = 600
3) Schedule
SAP_COLLECTOR_FOR_P
ERFMONITOR to run more
frequently.
4) Check version of saposcol
(saposcol –v). Different OS
versions has to run different
versions of saposcol.
/usr/sap/SID/SYS/exe/run/sa
poscol

AIM COMMON ERRORS & SOLUTIONS Page 22 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
10. Connection to partner Cause : Codepage settings of To find out if this is the
broken. SAP-Gateway sihp8034 (app) is different from cause of the problem,
on host sihp8042 (db) and sihp8035 run RSCP0001 /
sihp8042.ap.pg.com. (app). All servers that house A5*, RSCP0018 via se38.
Module niuxi.c. NI A6*, A7* have codepage set to
component. Error 1100 (default Latin-1 or ISO8859-
message during test 1). But sihp8034 was set to 1610
connection of TCP/IP via (ISO8859-9).
sm59
Solution :
RFC-TCPIP connection 1) Change the unix environment
from app server sihp8034 to variable of a6padm in
db server sihp8042 was not sihp8034. Env variable can be
working. Initial symptom found in
appeared when Thailand is /home/a6padm/.sapenv_sihp8
not able to transfer ASN 034.csh and .sh.
from A6P to the interface
server sihp8018. This was SAP_CODEPAGE = 1100 or
working in A6A, but not in don't set the env variable at
A6P. Note that the TCPIP all so it would take the
connection from another default 1100.
app server sihp8035 to the PATH_TO_CODEPAGE ->
db server is functioning deleted this variable since it
well. is not used
AIM COMMON ERRORS & SOLUTIONS Page 23 of 60
454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
11. Changes / Transports to Modify default.pfl parameter to
the database server are contain:
not seen from the
application server rdisp/bufrefmode=sendon,exeaut
o
12. /usr/sap/trans is full Run the scripts :
1) Go to /usr/sap/trans/data
2) /
usr/sap/trans/scripts/compan
dmove <# of days>
/usr/sap/trans/archive/datafil
es

AIM COMMON ERRORS & SOLUTIONS Page 24 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
SAP PRESENTATION

SAP GUI

AIM COMMON ERRORS & SOLUTIONS Page 25 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
1. Logon Load Balancing SAP system may be down for Broadcast planned
Error maintenance. Check the system outages
change tickets/c4415 Emphasize to users
messages for planned not to make manual
changes. changes to picklist.
User has manually entered the
picklist entry and the server has
changed. Ask user to get LCC
to reinstall picklist.
Check the services file in
C:\win95 for sapmsXXX and
sapdpXXX entries. Ask user to
get LCC to install latest service
file from GWR.
None of the above causes then
ask user to get LCC to reinstall
picklist.
Services file may have been
overwritten by a ESD job. Ask
Helpdesk to re-install the
Services file or re-install the
picklist.

AIM COMMON ERRORS & SOLUTIONS Page 26 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
2. Application Helpfiles not The Helpfile location This parameter
available parameters have not been set change has been
up. Set up the following effected on nearly all
parameters in the default profile the systems already
so issue should not
eu/iwb/path_win32 arise
=global/simpstd/plainhtm/helpdat
a/
eu/iwb/server_win32 =
intraprod7.internal.pg.com

and then rebounce the system.


3. Other applications Users load non-SEWP’d Users should not use
conflict with SAP GUI. applications on their non-SEWP’d
workstation which conflict with applications
SAP GUI. SEWP C&I the
applications.
4. Error msg with SAP NO SOLUTION as SAP GUI’s Users should not
GUI’s that were installed installed via CD are NOT install SAP GUI via
via CD supported by AIM or Basis CD

AIM COMMON ERRORS & SOLUTIONS Page 27 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
SAP PRINTING

AIM COMMON ERRORS & SOLUTIONS Page 28 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
1. SAP spool indicates that DIAGNOSIS
print job has successfully Try sending output from
completed but no print UNIX via lp
out. -d”<printername>”
<filename>
Use lpstat <unix printer
name> or lpstat -c
<request id> to see status
of your printout

If it is just queuing up and


not printing, then it is a unix
spooler problem

Job stuck at Unix level.


Use the printers command
to check that the printer
status is ENABLED, the
print queue is spelt
correctly and the status
check is o.k. If DISABLE
then ENABLE printer. If
print queue spelt
incorrectly, delete printer
AIM COMMON ERRORS & SOLUTIONS Page 29 of 60
454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
2. Spool table TSP01 Run RSPO0041 job with Basis to check batch job
reaches limit of 32000 transaction SE38 with logs
following variant, client : *
and check the delete all
print job with min age
option and Commit
parameter: 1000 can
check the table size with
the following SQL
statement in svrmgrl,
Select count(*) from
sapr3.tsp01;
3. Print jobs cannot be Printer configured Follow proper procedures
printed out. incorrectly at SAP or Unix for printer configuration.
level or both. Reconfigure
printer.
4. Print job at SAP & Unix Netware or local site
level is completed but infrastructure down.
printer does not print it Forward issue to local site
out. Cannot print from to handle.
other windows
applications like Microsoft
Word and Excel.

AIM COMMON ERRORS & SOLUTIONS Page 30 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
5. SAP Spool work process Large print job submitted
hung with many other print job
waiting. Ask user to
SM51 shows SPOOL delete print job and run it
process running the as two or smaller print
RSPOWP00 and CPU time jobs.
is very long for this work Too many print jobs
process created. Ask user to
delete some print jobs.
Large print job stuck at
Unix Level verified using
lpstat. Perform lpshut and
then lpsched to start/stop
the Unix print spooler.

AIM COMMON ERRORS & SOLUTIONS Page 31 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
6. SAP Spool work process  Large print job submitted
hung SM51 shows SPOOL with many other print job
process running the waiting. Ask user to delete
RSPOWP00 and CPU print job and run it as two
time is very long for this or smaller print jobs.
work process  Too many print jobs
created. Ask user to
delete some print jobs.
 Large print job stuck at
Unix Level verified using
lpstat. Perform lpshut and
then lpsched to start/stop
the Unix print spooler.
 If system responds with
scheduler already running:
- cd /usr/spool/lp
- ls
- rm SCHEDLOCK file if
present and stop/restart
the scheduler.

AIM COMMON ERRORS & SOLUTIONS Page 32 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
7. SAP ‘Output Status’  Printer inadvertently  Ensure complete end-to-
reports ‘error’ deleted. Send SC back to end setup and testing has
customer requesting been performed for new
/usr/bin/lp: destination xxx original info and recreate printer requests.
non-existent (use SSC#253)  Ensure printer deletion
 Printer created on SAP but CBA is followed correctly.
not UNIX. Create on UNIX
using printer script and
retest at UNIX and SAP
level.

AIM COMMON ERRORS & SOLUTIONS Page 33 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
8. SAP ‘Output Status’  Spool temp files get
reports ‘wait’ corrupted. Use UNIX
printer script to check
printer and spooler status.
Perform ps –ef|grep on lp,
note the printer that is
hung, shutdown the
scheduler via lpshut, kill
any remaining lp
processes, cd
/var/opt/spool/lp/requests
to view what’s in the temp
queue and remove, restart
lpsched

 Delete
/usr/sap/L71/DVEBGMS
00/data/SP*
 Clean up stats file via st03
 Clean up work process
trace files via sm50
 Recycle spooler

AIM COMMON ERRORS & SOLUTIONS Page 34 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
9. EMEA Printing Support EMEA Printing Servers:
etsp0033; etsp3005
 remsh etsp0033 -l
prtmgr "lpstat -p
ETC920R"
 smitty
10.No printing possible. 2 Possible solutions
SM21 system logs show 1. Reorg the TemSe
the following errors, Database using
cannot open transaction SP12. TemSe
/usr/sap/<SID>/DVEBMGS00 Database->Reorganisation
/data/stat Delete obsolete requests
cannot open 2. remove all SPxxxxB files

/usr/sap/<SID>/DVEBMGS00 from the Unix directory


/data/SPxxxxB /usr/sap/<SID>/DVEBMGS
00/data
Above errors appear even
thought the filesystem is not
100% utilized

AIM COMMON ERRORS & SOLUTIONS Page 35 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
11. Overflow of spool 1. Deleted / Reorg Temse via
database sp12
2. Check variant of
SAP_REORG_SPOOL
housekeeping job

AIM COMMON ERRORS & SOLUTIONS Page 36 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
SAP BACKUPS

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.]

AIM COMMON ERRORS & SOLUTIONS Page 37 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
1. RC=1 Backup ended Just a warning msg with no Look at the logs and see
successfully with critical implications the messages that were
warnings flashed. Let the system
owners know if you see
something particularly
abnormal.
Make sure you check
the
/var/opt/ctm/ctma/sysout
file to verify that nothing
has been missed.

AIM COMMON ERRORS & SOLUTIONS Page 38 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
2. sihp8040. 2 Possible reasons:
Check the logs under
sapg900_cleanup_pool.sh /var/opt/ctm/ctma/sysout : ll | grep
failed with rc=1 900
1. Mostly because there are no
logs that qualify to be deleted,
this is not a issue at all
2. Some error really happened
during the cleanup process

Action for Issue


1. Close the ticket with no
action.
2. Fire the cleanup job again
under /var/opt/sapg/scripts

#./sapg900_cleanup_pool.sh +3
var/opt/saparch/prod
#./sapg900_cleanup_pool.sh +10
var/opt/saparch/dvlp

AIM COMMON ERRORS & SOLUTIONS Page 39 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
3. Tablespace XXXX is Last backup ended abruptly or
already in backup mode was killed

Two ways to handle this:


1. Manually end backup mode
via Oracle commands

sesu - orasid
svrmgrl
connect internal;
select * from
V$BACKUP;
alter tablespace
<tablespacename> end
backup;

2. Fire script
/opt/nb/bin/backoff_backup.sh
<SID>

AIM COMMON ERRORS & SOLUTIONS Page 40 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
4. lock.bra exists Last backup ended abruptly or
was killed

1. Remove the file from


/oracle/SID/sapbackup and
rerun
2. Under /opt/nb/bin fire the
script

./removelock.sh SID

5. pgbrclean.sh not found The script is missing from the


/sapmnt/SID/exe directory

Copy over the script from the


/opt/nb/bin directory and in case it
is missing from there, ftp it from
another source to /bin and copy it
to /etc. The backup would
normally be successful, so don’t
rerun the backup, just fire the
script as ora<sid>

AIM COMMON ERRORS & SOLUTIONS Page 41 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
6. backint execute Problem with the permissions of
permission denied backint. Usually the sticky bit
would be missing.

Check the permissions for the


backint file under
/usr/openv/netbackup/bin.

If it is different from -rwsr-sr-t


redirect to regional UIT to change
the permissions.

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

AIM COMMON ERRORS & SOLUTIONS Page 42 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
8. Two errors while Auto-secure problem. Define sapdba role to
executing a backup may Sapdba_role does not exist OPS$SIDADM account
say the following [ by running
sapdba_role.sql]
1. $sesu - ora<sid>
- invalid [Switch user to
username/password: logon ora<sid>]
denied 2. $cdexe
Connect to database [Changes to
instance SID failed directory
/usr/sap/<SID>/SYS/e
- ORA-00942: table or xe/run]
view does not exist 3. Execute
BR303E Determination of sapdba_role.sql with
Oracle RDBMS version the following
failed parameters: $sqlplus
internal
@sapdba_role <SID>
UNIX

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)

AIM COMMON ERRORS & SOLUTIONS Page 45 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
12. /var/opt/saparch in 1)Attempt to delete using
pooldisk is 100% full /var/opt/sapg/scripts/sap
g900_cleanup_pool.sh +
x /var/opt/saparch

2)Run backup of pooldisk

 /
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]

STAT MESSAGE ACTION


US
13 file read failed 1/netbackup problem -->
UIT
23 socket read failed -> UIT
25 cannot connect on socket 1/rerun
2/send to UIT
40 network connection broken 1/rerun
2/send to UIT
41 network connection timed out 1/rerun
2/send to UIT
49 client did not start 1/ configuration error or
autosecure problem,
send to UIT
52 timed out waiting for media manager to 1/ rerun
mount volume 2/send to UIT
84 media write error 1/remove tape
2/rerun job
85 media read error 1/rerun job
2/send to UIT

AIM COMMON ERRORS & SOLUTIONS Page 47 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
227 no entity was found 1/setup problem, send to
UIT
230 the specified class does not exist in the 1/setup problem, send to
configuration database UIT

AIM COMMON ERRORS & SOLUTIONS Page 48 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
SAP SECURITY

AIM COMMON ERRORS & SOLUTIONS Page 49 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
1. Symptom 1: R3trans -d ; Listener.ora listens to incoming EXPLANATION
/usr/sap/trans/bin tp IPC connections only. But the
connect <SID> gives client tries to connect using Taking A5P as
error message: TCP/IP as defined in example:
“2EETW169 no connect tnsnames.ora. Listener.ora
possible: ‘DBMS = configuration has three
ORACLE 1) Modify settings:
tns_names_ora= ‘<SID>’. /oracle/<SID>/listener.ora to
Log shows: sql error contain only (ADDRESS= 1) IPC with KEY
1017 (PROTOCOL= TCP)(Host= A5P.world
sihp8029)(Port= 1527) in the 2) IPC with KEY A5P
Symptom 2: Joining address list. 3) TCP/IP at port 1527
<sid>adm to DBA group 2) Stop and Start listener -Community sap.world
solves problem at UNIX (lsnrctl stop; lsnrctl start)
level, but does not solve SQLNET.ORA has
problem at SAP level. Tp * This can be done online. AUTOMATIC_IPC = ON
check from within R/3 Stopping listener prevents new [This means IPC is
fails (STMS à Overview à incoming connections (new preferable to TCP/IP if
Systems à Select SID à transports,..), but all connections available]
R/3 System à Check à started by processes when SAP If ORACLE CLIENT is in
Transport Tool) was restarted still can connect to the same box client can
the database even when listener connect through IPC.
is not up. But this will not help for
Application Server.
AIM COMMON ERRORS & SOLUTIONS Page 50 of 60
454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
2. SourceOne is not able UIT included the CoDi program
to receive data from A5P (/opt/cdirect/cdunix/ndm/
(sihp8040). bin/ndmsmgr) in the Autosecure
config file privpgms.init which
When security rules were means this program is actually
enforced, “cdirect” id is no trusted to switch user id while it is
longer able to surrogate to running. Consequently, specific
sapsys group. rules in Autosecure database is
no longer needed.
3. Backup returns error /usr/openv/netbackup/bin/backint
when autosecure rules should be owned by root:sys and
were put in forced mode permissions 7755.

Forward ticket to UIT to do this


change: “chmod 7755
/usr/openv/netbackup/bin/
backint”

AIM COMMON ERRORS & SOLUTIONS Page 51 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
4. Backup failing due to SAPDBA role has not been Whenever chdbpass is
SQL error -942 defined yet and <sid>adm is not executed and
granted SAPDBA role. OPS$<sid>adm is
recreated, you need to
DIAGNOSIS: run sapdba_role script
1) sesu - ora<sid> afterwards.
2) svrmgrl
3) connect internal 1) sesu - ora<sid>
4) select * from dba_role_privs; 2) cdexe
5) OPS$<sid>adm should have 3) sqlplus internal
CONNECT, RESOURCE, @sapdba_role <SID>
SAPDBA role assigned to him. UNIX
If SAPDBA role is not assigned
to him, do the ff.

SOLUTION:
1) sesu - ora<sid>
2) cdexe
3) sqlplus internal
@sapdba_role <SID> UNIX

AIM COMMON ERRORS & SOLUTIONS Page 52 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
5. <sid>adm can still do <sid>adm should not be able to
svrmgrl and connect to connect to the database. Only
the database <ora>sid should be part of DBA
group

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

AIM COMMON ERRORS & SOLUTIONS Page 53 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
6. Where are the new 1) Backup scripts:
backup scripts and ITO (pgsapbackup.sh,
monitoring scripts that pgsaparchive.sh,
work with Phase I saparch_guard.sh,
security? pgbrclean.sh).

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

Monitoring scripts work with


secured and non-secured
systems. Old backup scripts for
non-secured systems are in:
AIM COMMON ERRORS & SOLUTIONS Page 54 of 60
454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
7. zpas doesn’t work for Your user account has not been
some systems created in the system or your
zpas reports error in account on the said system is
the status locked.. Zpas (password
Tried to login using propagation) only works for those
new password that systems where your account
was propagated by exists. Open ITSM ticket SSC
zpas but cannot login 985.

8. zpas works to Password you provided zpas is Provide a unique


propagate new password not unique. Password you password.
to a system but when you provided was one of the last 5
login, system asks you to passwords you’ve already used.
immediately change your
password. Effect is your
passwords across all
systems are not
synchronized anymore

AIM COMMON ERRORS & SOLUTIONS Page 55 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
9. How to know which AIM is using 2 policy models for
policy model a particular hp:
server is subscribed to? 1 - hp_sap_sec@bdhp4176 :
This is the highly secured policy
model for all Production systems
2 - hp_sap_std@bdhp4176 :
This is the standard policy model
for all non-production systems

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.

AIM COMMON ERRORS & SOLUTIONS Page 56 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
10. How to change Option 1:
password of system via SAPDBA
without knowing old Option 2:
password 1) sesu – orasid
2) svrmgrl
3) connect internal
4) alter user system identified
by <new password>
11. How to check the 1. sesu to root
autosecure audit logs? 2. seaudit - sd 09-mar-2001 –a
| grep “* W *”

AIM COMMON ERRORS & SOLUTIONS Page 57 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
ERROR MSG/SYMPTOM POSSIBLE CAUSE & PREVENTIVE ACTION
SUGGESTED SOLUTION
12. Connect internal 1) Modify
as <sid>adm requests for /oracle/<sid>/rdbms/lib/config.c
a password.
# ifdef SEQ_PSX
Startup and shutdown using #define SS_OPER_GRP "dba"
“startsap”, “stopsap” #else
hangs during start up and #define SS_OPER_GRP
shutdown of database "oper"
# endif /* SEQ_PSX */

char *ss_dba_grp[] =
{SS_DBA_GRP,
SS_OPER_GRP};

2) Stop listener. Stop SAP and


Oracle
3) Relink oracle using relink.sh
script as ora<sid>. Relink can
be found on
sihp8044:/oracle/oraanq home
directory.

AIM COMMON ERRORS & SOLUTIONS Page 58 of 60


454382796.doc last saved 4/19/2012 04:38:00 PM
AIM COMMON ERRORS & SOLUTIONS Page 59 of 60
454382796.doc last saved 4/19/2012 04:38:00 PM
AIM COMMON ERRORS & SOLUTIONS Page 60 of 60
454382796.doc last saved 4/19/2012 04:38:00 PM

You might also like