Nach der Systemkopie ist vor der Systemkopie

Nach einer erfolgreichen Systemkopie einer MCOD Datenbank in der sich sowohl der ABAP Part eines SAP Systems als auch der JAVA Part befindet gibt es ein Problem mit den gesetzten Synomymen, wenn man für die Kopie den JAVA Teil per Instalaltion wieder herstellt.

Dies sorgt dann dafür, dass der <sid>adm keine Datenbankaktionen mehr antriggern kann. Innerhalb des ABAP Systems äußert sich das zum Beispiel so, dass in der Transaktion DB02 der Baum für die Datenbank-Jobverwaltung gänzlich fehlt. Dieser ist dann auch nicht über die DB13 erreichbar. Ebenso ist es nicht möglich alsadm auf der Shell ein brconnect -f check auszuführen:

server:adm 31> brconnect -f check
 BR0801I BRCONNECT 7.20 (24)
 BR0805I Start of BRCONNECT processing: cejzkkdm.chk 2012-11-29 16.21.38
 BR0484I BRCONNECT log file: /oracle//sapcheck/cejzkkdm.chk
 BR0280I BRCONNECT time stamp: 2012-11-29 16.21.39
 BR0301E SQL error -1017 at location db_connect-2, SQL statement:
 'CONNECT system/*******'
 ORA-01017: invalid username/password; logon denied
 BR0310E Connect to database instance  failed
 BR0280I BRCONNECT time stamp: 2012-11-29 16.21.39
 BR0301E SQL error -1017 at location db_connect-2, SQL statement:
 'CONNECT system/*******'
 ORA-01017: invalid username/password; logon denied
 BR0310E Connect to database instance failed
 BR0806I End of BRCONNECT processing: cejzkkdm.chk 2012-11-29 16.21.39
 BR0280I BRCONNECT time stamp: 2012-11-29 16.21.39
 BR0804I BRCONNECT terminated with errors
 server:adm 32>

Abhilfe schaffen hier zum Beispiel die brtools respektive brconnect. Mittels eines beherzten brconnect -u / -c -f crsyn -o SAP<SCHEMA> kann der geneigte Admin das Synoym entsprechend passend anlegen lassen. Die Option -u / sorgt dafür, dass der OPS$ Connect genutzt (ora<SID>) wird und kein Datenbankuser oder Passwort mitgeben muss. Das sieht dann so aus:

server:ora<SID> 3> brconnect -u / -c -f crsyn -o SAP<SCHEMA>
BR0801I BRCONNECT 7.20 (24)

BR0280I BRCONNECT time stamp: 2012-11-29 16.25.29
BR0833I Creating public synonyms for database log owner SAP<SCHEMA> ...

BR0925I Public synonym SAP_SDBAH created successfully for table SAP<SCHEMA>.SDBAH
BR0925I Public synonym SAP_SDBAD created successfully for table SAP<SCHEMA>.SDBAD
BR0925I Public synonym SAP_MLICHECK created successfully for table SAP<SCHEMA>.MLICHECK
BR0925I Public synonym SAP_SAPLIKEY created successfully for table SAP<SCHEMA>.SAPLIKEY
BR0925I Public synonym SAP_DBAML created successfully for table SAP<SCHEMA>.DBAML
BR0925I Public synonym SAP_DBARCL created successfully for table SAP<SCHEMA>.DBARCL
BR0925I Public synonym SAP_DBAFID created successfully for table SAP<SCHEMA>.DBAFID
BR0925I Public synonym SAP_DBAEXTL created successfully for table SAP<SCHEMA>.DBAEXTL
BR0925I Public synonym SAP_DBAREOL created successfully for table SAP<SCHEMA>.DBAREOL
BR0925I Public synonym SAP_DBABARL created successfully for table SAP<SCHEMA>.DBABARL
BR0925I Public synonym SAP_DBADFL created successfully for table SAP<SCHEMA>.DBADFL
BR0925I Public synonym SAP_DBAOPTL created successfully for table SAP<SCHEMA>.DBAOPTL
BR0925I Public synonym SAP_DBASPAL created successfully for table SAP<SCHEMA>.DBASPAL
BR0925I Public synonym SAP_DBABD created successfully for table SAP<SCHEMA>.DBABD
BR0925I Public synonym SAP_DBABL created successfully for table SAP<SCHEMA>.DBABL
BR0925I Public synonym SAP_DBATL created successfully for table SAP<SCHEMA>.DBATL
BR0925I Public synonym SAP_DBAOBJL created successfully for table SAP<SCHEMA>.DBAOBJL
BR0925I Public synonym SAP_DBAPHAL created successfully for table SAP<SCHEMA>.DBAPHAL
BR0925I Public synonym SAP_DBAGRP created successfully for table SAP<SCHEMA>.DBAGRP
BR0925I Public synonym SAP_DBAERR created successfully for table SAP<SCHEMA>.DBAERR
BR0925I Public synonym SAP_DBATRIAL created successfully for table SAP<SCHEMA>.DBATRIAL
BR0925I Public synonym SAP_SVERS created successfully for table SAP<SCHEMA>.SVERS
BR0925I Public synonym SAP_CVERS created successfully for table SAP<SCHEMA>.CVERS
BR0925I Public synonym SAP_TGORA created successfully for table SAP<SCHEMA>.TGORA
BR0925I Public synonym SAP_IGORA created successfully for table SAP<SCHEMA>.IGORA
BR0925I Public synonym SAP_TSORA created successfully for table SAP<SCHEMA>.TSORA
BR0925I Public synonym SAP_TAORA created successfully for table SAP<SCHEMA>.TAORA
BR0925I Public synonym SAP_IAORA created successfully for table SAP<SCHEMA>.IAORA
BR0925I Public synonym SAP_DD02L created successfully for table SAP<SCHEMA>.DD02L
BR0925I Public synonym SAP_DD09L created successfully for table SAP<SCHEMA>.DD09L
BR0925I Public synonym SAP_DDNTT created successfully for table SAP<SCHEMA>.DDNTT
BR0925I Public synonym SAP_DBCHK created successfully for table SAP<SCHEMA>.DBCHK
BR0925I Public synonym SAP_DBDIFF created successfully for table SAP<SCHEMA>.DBDIFF
BR0925I Public synonym SAP_DBSTATC created successfully for table SAP<SCHEMA>.DBSTATC
BR0925I Public synonym SAP_DBSTATTORA created successfully for table SAP<SCHEMA>.DBSTATTORA
BR0925I Public synonym SAP_DBSTATIORA created successfully for table SAP<SCHEMA>.DBSTATIORA
BR0925I Public synonym SAP_DBSTATHORA created successfully for table SAP<SCHEMA>.DBSTATHORA
BR0925I Public synonym SAP_DBSTAIHORA created successfully for table SAP<SCHEMA>.DBSTAIHORA
BR0925I Public synonym SAP_DBCHECKORA created successfully for table SAP<SCHEMA>.DBCHECKORA
BR0925I Public synonym SAP_DBMSGORA created successfully for table SAP<SCHEMA>.DBMSGORA

BR0280I BRCONNECT time stamp: 2012-11-29 16.25.30
BR0834I Public synonyms for database log owner SAP<SCHEMA> created successfully

BR0280I BRCONNECT time stamp: 2012-11-29 16.25.30
BR0802I BRCONNECT completed successfully
server:ora<SID> 4>

Durch die Installation des JAVA Stacks bei der Systemkopie sind leider auch einige Profildateien der Datenbank ersetz worden. Die sorgt dann zum Beispiel dafür, dass die Backups nicht mehr gestartet werden können. Ein Blick init<SID>.ora und die init<SID>.utl empfiehlt sich hier auf jeden Fall.

Die Dateien findet man in der Regel hier: $ORACLE_HOME/dbs/

About the author