Archive stuck

Hi,
Our stage system faced an almost archive stuck situation where the 'oraarch' directory was 99% full. I moved some of the redo log files to a different location and re-triggered the BRARCHIVE job which completed successfully (copy,delete,save). Now, I put back the redo log files which were moved from the oraarch directory but these files are not touched by BRARCHIVE job. I understand that the redo log files are incremental in nature which means that my latest redo log files contain all the changes. Are these files not being cleared by BRARCHIVE because of a clash in the sequence numbers? or is there any other means to force BRARCHIVE to process these files ?
Cheers!!
Aj

Hi Anindya,
Thanks for your time. As per your explanation, let me cite an example.
Lets say, we have redo log files 20 to 30 in the oraarch directory at the time of an archive stuck situation. In this case, I should have moved the files, like 26 - 30 to a temporary location.
- Run BRARCHIVE (This processes the redo log files 20 - 25)
- Restore the file 26 - 30 to oraarch which will now have the redo logs 31 - ...(The new redo log files)
-Run BRARCHIVE
-This time it will include 26 - 30 as the sequence would be correct.
Pls correct me if I am wrong.
Thanks for correcting me on Redo log files not being incremental. I see why, because incase of a recovery we would need all the redo log files. If it is incremental, then the latest redo log would be sufficient for the recovery which is actually not the case.
Cheers!!
Aj

Similar Messages

Logical Standby out of sync after archiver stuck (how to resync)

Hi,
I had an archiver stuck on my logical standby database for about 4 hours this night.
2 hours later my primary db also had an archiver stuck.
After solving the problem by repairing the backup mechanism and startup of the archivelog backup I realised
that some tables are out of sync.
How can I get back all things back in sync again?
DB: 11gR2 EE
OS: RedHat Linux 5.5
Thanks
941743

Hi,
I don't sure have or not resyncronization whole schema, but you can use with PL/SQL as
Stop SQL Apply on logical standby database
SQL> ALTER DATABASE STOP LOGICAL STANDBY APPLY;
on primary
SQL> begin
2> for t in (select table_name from db_tables where owner = '<your schema name>')
3> loop
4> DBMS_LOGSTDBY.INSTANTIATE_TABLE(shema_name => '<your schema name>', object_name => T.Table_name, dblink => '<you dblink name>');
5> end loop;
6>end;
Start SQL Apply on logical standby database
SQL> ALTER DATABASE START LOGICAL STANDBY APPLY IMMEDIATE;If you skip DML and DDL for your schema, then you must UNSKIP DML and DDL on this tables you must add following script to PL/SQL block before INSTANTIATE_TABLEs.
DBMS_LOGSTDBY.UNSKIP(stmt => 'DML', schema_name => '<your schema name>', object_name => T.Table_Name);
DBMS_LOGSTDBY.UNSKIP(stmt => 'DDL', schema_name => '<your schema name>', object_name => T.Table_Name);Regards
Mahir M. Quluzade
Edited by: Mahir M. Quluzade on Sep 13, 2012 6:17 PM

No Archiver Stuck on 11g

Hello.
I am trying to "achieve" a archiver stuck situation on an Oracle 11g installation (running SAP ERP 6.0).
However i am unable to make the database hang, something that is straight-forward with 10g.
I have browsed some documentation for 11g without finding any info on what's new in this regard.
Can someone tell me why the Oracle database does not hang when the archive directory is full (log_archive_dest_1) on 11g ?
This is a common problem on earlier versions, the SAP system hangs, no logon is possible and the alert_monitor triggers an unavailability alert.

Nothing has changed, fill up your archive directory. Then the online redo has to be full as well so you might have to run some dummy statement like 'update <large_table> set fieldx = fieldx' to achieve that.
Cheers Michael
Edit: or switch the logfiles...

PREPARE Stuck in IMPORT Phase

We are Upgrading SRM Development Server . ( Oracle 10G on HPUX)
My PREPARE Phase is Running IMPORT Module NPREPCRE0 Subphase .
This Phase is running from more than 24 hr .
As per document ( Upgrade Guide I cannot Stop PREPARE in these phase .)
Please Find the SAPupCheck Logs
********START******************
************************* SAPup started in PREPARE mode *************************
This is SAPup version 7.00/2 patch level 24.067.
Environment for SAPup:
SAPSID              = SRD
SAPHOST             = eux353
STARTPATH           =
KERNPATH            = /usr/sap/SRD/SYS/exe/run
PROFPATH            = /usr/sap/SRD/SYS/profile
LOCAL SLOG          =
LOCAL SLOG (OLD)    =
CENTRAL SLOG        =
CENTRAL SLOG (OLD) =
EPS INBOX           =
EPS ROOT            =
DBASID              =
DBAHOST             =
DBAPWD              = <NOT REPORTED>
NR R3TRANS          = 3
NR R3LOAD           = 1
IMPORT DESTTIME     = 86400
STARTR3             = ""
STARTPARAMS R3      = ""
STOPR3              = ""
STOPPARAMS R3      = ""
STARTDB             = ""
STARTPARAMS DB      = ""
STOPDB              = ""
STOPPARAMS DB      = ""
UPGRADE USER        =
UPGRADE LANGUAGE    = E
SLOGNAME            = SLOG
ALOGNAME            = ALOG
SYSNUM              =
PROFNAME            =
DDIC PWD            = <NOT REPORTED>
GATEWAY HOST        =
GATEWAY SERVICE     =
MS SERVICE          = 0
SLOW SHADOW IMPORT = Y
MAX BUFREFTIME      = 120
BATCH HOST          =
NR BTC-PROCS INTERN = 3
CUSTOMER GENERATION = 0
SAP START PROFILE   =
DEFPROFNAME         =
OSTYPE              = HP-UX IA64
OSVERS              = 11.23
DESTVERS            = 700
COMPDESTVERS        = PI_BASIS=2005_1_700,SAP_ABA=700,SAP_AP=700,SAP_BASIS=700,SAP_BW=700,SRM_PLUS=550,SRM_SERVER=550,ST-PI=2005_1_700
SUBSTSTVERS         = 700
COMPSUBSTSTVERS     = SAP_BASIS=700,SAP_ABA=700,SAP_BW=700,SRM_SERVER=550
DESTPRODSHORTID     = R/3
DESTPRODSHORTREL    = 700
IMPORT LANGUAGES    =
DB REPSWITCH PAR    = NOT_SPECIFIED
PARALLEL DDLNTABS   = 0
TABLSIZE            = 0
KERNEL BIT SELECTION = 64 bit, no choice
SHD INSTANCE NUMBER =
SHD send d talk port      = -1
SHD send d listen port    = -1
SHD collect d listen port = -1
SHD collect d talk port   = -1
SHD GW SERVICE            =
SHD MS SERVICE            =
SHD HOST                  =
SHD GW HOST               =
SHD STARTPATH             = /usr/sap/put/SRD/homeshd/SRD
SHD R3 START PROFILE      =
SHD PROFILE PATH          = /usr/sap/put/SRD/SYS/profile
SHD PROFILE NAME          =
SHD startsap              =
SHD stopsap               =
SHD workpath              =
SHD kernpath              = /usr/sap/put/exe
dba schema                =
dba shd schema            =
connect env string        =
REMOTE UPGRADE DIRECTORY =
SAP SERVICE ACCOUNT          =
SAP SERVICE ACCOUNT PWD= <NOT REPORTED>
Original shadow profile     =
PREPARE STARTED AT 20080107072449 ***
...begin dialogue at 20080107072450
...end dialogue at 20080107072516
...begin dialogue at 20080107072519
...end dialogue at 20080107072529
...begin dialogue at 20080107072529
...end dialogue at 20080107072535
...begin dialogue at 20080107072538
...end dialogue at 20080107072559
...begin dialogue at 20080107072603
...end dialogue at 20080107072649
...begin dialogue at 20080107072652
************************* SAPup started in PREPARE mode *************************
This is SAPup version 7.00/2 patch level 24.067.
Condition level 1, total => TRUE '#if ( "ORA" == "ORA" )' => TRUE
...begin dialogue at 20080107074628
...end dialogue at 20080107075039
...STARTED at 20080107075039.
Environment for SAPup:
SAPSID              = SRD
SAPHOST             = eux353
STARTPATH           =
KERNPATH            = /usr/sap/SRD/SYS/exe/run
PROFPATH            = /usr/sap/SRD/SYS/profile
LOCAL SLOG          =
LOCAL SLOG (OLD)    =
CENTRAL SLOG        =
CENTRAL SLOG (OLD) =
EPS INBOX           = /in
EPS ROOT            =
DBASID              =
DBAHOST             =
DBAPWD              = <NOT REPORTED>
NR R3TRANS          = 3
NR R3LOAD           = 1
IMPORT DESTTIME     = 86400
STARTR3             = ""
STARTPARAMS R3      = ""
STOPR3              = ""
STOPPARAMS R3      = ""
STARTDB             = ""
STARTPARAMS DB      = ""
STOPDB              = ""
STOPPARAMS DB      = ""
UPGRADE USER        =
UPGRADE LANGUAGE    = E
SLOGNAME            = SLOG
ALOGNAME            = ALOG
SYSNUM              =
PROFNAME            =
DDIC PWD            = <NOT REPORTED>
GATEWAY HOST        =
GATEWAY SERVICE     =
MS SERVICE          = 0
SLOW SHADOW IMPORT = Y
MAX BUFREFTIME      = 120
BATCH HOST          =
NR BTC-PROCS INTERN = 3
CUSTOMER GENERATION = 0
SAP START PROFILE   =
DEFPROFNAME         =
OSTYPE              = HP-UX IA64
OSVERS              = 11.23
DESTVERS            = 700
COMPDESTVERS        = PI_BASIS=2005_1_700,SAP_ABA=700,SAP_AP=700,SAP_BASIS=700,SAP_BW=700,SRM_PLUS=550,SRM_SERVER=550,ST-PI=2005_1_700
SUBSTSTVERS         = 700
COMPSUBSTSTVERS     = SAP_BASIS=700,SAP_ABA=700,SAP_BW=700,SRM_SERVER=550
DESTPRODSHORTID     = R/3
DESTPRODSHORTREL    = 700
IMPORT LANGUAGES    =
DB REPSWITCH PAR    = NOT_SPECIFIED
PARALLEL DDLNTABS   = 0
TABLSIZE            = 0
KERNEL BIT SELECTION = 64 bit, no choice
SHD INSTANCE NUMBER =
SHD send d talk port      = -1
SHD send d listen port    = -1
SHD collect d listen port = -1
SHD collect d talk port   = -1
SHD GW SERVICE            =
SHD MS SERVICE            =
SHD HOST                  =
SHD GW HOST               =
SHD STARTPATH             = /usr/sap/put/SRD/homeshd/SRD
SHD R3 START PROFILE      =
SHD PROFILE PATH          = /usr/sap/put/SRD/SYS/profile
SHD PROFILE NAME          =
SHD startsap              =
SHD stopsap               =
SHD workpath              =
SHD kernpath              = /usr/sap/put/exe
dba schema                =
dba shd schema            =
connect env string        =
REMOTE UPGRADE DIRECTORY =
SAP SERVICE ACCOUNT          =
SAP SERVICE ACCOUNT PWD= <NOT REPORTED>
Original shadow profile     =
...begin dialogue at 20080107075039
...end dialogue at 20080107075333
...begin dialogue at 20080107075333
...end dialogue at 20080107075440
...begin dialogue at 20080107075440
...end dialogue at 20080107075815
...begin dialogue at 20080107075815
...end dialogue at 20080107075932
Execution of PREPARE module Parameter input begins at 20080107075932
UPGRADEPHASE
UPGRADEPHASE BEGIN_PRE
...started at 20080107075932
Condition level 1, total => FALSE '#if "ORACLE" == "SAPDB"' => FALSE
Condition level 1, total => FALSE '#elseif "ORACLE" == "DB2-z/OS"' => FALSE
Condition level 1, total => FALSE '#elseif "ORACLE" == "DB2/400"' => FALSE
Condition level 1, total => FALSE '#elseif "ORACLE" == "DB6"' => FALSE
Condition level 1, total => FALSE '#elseif "ORACLE" == "INFORMIX"' => FALSE
Condition level 1, total => FALSE '#elseif "ORACLE" == "MSSQL"' => FALSE
Condition level 1, total => TRUE '#elseif "ORACLE" == "ORACLE"' => TRUE
Condition level 1, total => FALSE '#if "HP-UX IA64" ~= "Linux"' => FALSE
Condition level 1, total => FALSE '#elseif "HP-UX IA64" ~= "Windows NT INTEL"' => FALSE
Condition level 1, total => FALSE '#elseif "HP-UX IA64" ~= "Windows NT IA64"' => FALSE
Condition level 1, total => FALSE '#elseif "HP-UX IA64" ~= "Windows NT X86_64"' => FALSE
Condition level 1, total => FALSE '#elseif "HP-UX IA64" ~= "AIX"' => FALSE
Condition level 1, total => TRUE '#elseif "HP-UX IA64" ~= "HP-UX"' => TRUE
..finished at 20080107075932 with status SUCCEEDED.
UPGRADEPHASE KEY_CHK
...started at 20080107075932
Phase log file: 'KEYCHK.LOG'
Correction package not found
...begin dialogue at 20080107075932
...end dialogue at 20080107080308
Correction package not found
...begin dialogue at 20080107080308
...end dialogue at 20080107080410
Correction package not found
...begin dialogue at 20080107080410
...end dialogue at 20080107081501
Correction package found
Correction package extracted
TOOLFIX VERSION: 24
TOOLFIX NAME: FIX_SRM50SR2
TOOLFIX DATE: 2007-11-27
...begin dialogue at 20080107081501
...end dialogue at 20080107081723
..finished at 20080107081723 with status SUCCEEDED.
UPGRADEPHASE EXTRACTKRN_PRE
...started at 20080107081723
Phase log file: 'EXTRKRN.LOG'
Condition level 1, total => FALSE '#if ( "0" == "1" )' => FALSE
Condition level 1, total => FALSE '#if ( "0" == "1" )' => FALSE
...begin dialogue at 20080107081723
...end dialogue at 20080107082152
Condition level 1, total => TRUE '#if "ORACLE" == "ORACLE" ' => TRUE
Condition level 1, total => TRUE '#if "ORACLE" == "ORACLE" ' => TRUE
..finished at 20080107082301 with status SUCCEEDED.
UPGRADEPHASE INITPUT_PRE
...started at 20080107082301
...begin dialogue at 20080107082302
...end dialogue at 20080107082615
...begin dialogue at 20080107082615
...end dialogue at 20080107082632
...begin dialogue at 20080107082632
...end dialogue at 20080107082657
...begin dialogue at 20080107082657
...end dialogue at 20080107082750
...begin dialogue at 20080107082750
...end dialogue at 20080107083036
...begin dialogue at 20080107083036
...end dialogue at 20080107083209
...begin dialogue at 20080107083209
...end dialogue at 20080107083235
...begin dialogue at 20080107083235
...end dialogue at 20080107083300
...begin dialogue at 20080107083300
...end dialogue at 20080107083322
Condition level 1, total => FALSE '#if -52 >= 0' => FALSE
Condition level 1, total => FALSE '#if -52 >= 0' => FALSE
Environment for SAPup:
SAPSID              = SRD
SAPHOST             = eux353
STARTPATH           = /home/srdadm
KERNPATH            = /usr/sap/SRD/SYS/exe/run
PROFPATH            = /usr/sap/SRD/SYS/profile
LOCAL SLOG          = /usr/sap/SRD/DVEBMGS40/log/SLOG40
LOCAL SLOG (OLD)    = /usr/sap/SRD/DVEBMGS40/log/SLOGO40
CENTRAL SLOG        = /usr/sap/SRD/SYS/global/SLOGJ
CENTRAL SLOG (OLD) = /usr/sap/SRD/SYS/global/SLOGJO
EPS INBOX           = /usr/sap/SRDtrans/EPS/in
EPS ROOT            = /usr/sap/SRDtrans/EPS
DBASID              = SRD
DBAHOST             = eux353
DBAPWD              = <NOT REPORTED>
NR R3TRANS          = 3
NR R3LOAD           = 1
IMPORT DESTTIME     = 86400
STARTR3             = "startsap_eux353_40"
STARTPARAMS R3      = "R3"
STOPR3              = "stopsap_eux353_40"
STOPPARAMS R3      = "R3"
STARTDB             = "startsap_eux353_40"
STARTPARAMS DB      = "DB"
STOPDB              = "stopsap_eux353_40"
STOPPARAMS DB      = "DB"
UPGRADE USER        = srdadm
UPGRADE LANGUAGE    = E
SLOGNAME            = SLOG700
ALOGNAME            = ALOG700
SYSNUM              = 40
PROFNAME            = /usr/sap/SRD/SYS/profile/SRD_DVEBMGS40_eux353
DDIC PWD            = <NOT REPORTED>
GATEWAY HOST        = eux353
GATEWAY SERVICE     = sapgw40
MS SERVICE          = 3640
SLOW SHADOW IMPORT = Y
MAX BUFREFTIME      = 120
BATCH HOST          = eux353
NR BTC-PROCS INTERN = 3
CUSTOMER GENERATION = 0
SAP START PROFILE   = START_DVEBMGS40_eux353
DEFPROFNAME         = /usr/sap/SRD/SYS/profile/DEFAULT.PFL
OSTYPE              = HP-UX IA64
OSVERS              = 11.23
DESTVERS            = 700
COMPDESTVERS        = PI_BASIS=2005_1_700,SAP_ABA=700,SAP_AP=700,SAP_BASIS=700,SAP_BW=700,SRM_PLUS=550,SRM_SERVER=550,ST-PI=2005_1_700
SUBSTSTVERS         = 700
COMPSUBSTSTVERS     = SAP_BASIS=700,SAP_ABA=700,SAP_BW=700,SRM_SERVER=550
DESTPRODSHORTID     = R/3
DESTPRODSHORTREL    = 700
IMPORT LANGUAGES    =
DB REPSWITCH PAR    = NOT_SPECIFIED
PARALLEL DDLNTABS   = 0
TABLSIZE            = 0
KERNEL BIT SELECTION = 64 bit, no choice
SHD INSTANCE NUMBER =
SHD send d talk port      = -1
SHD send d listen port    = -1
SHD collect d listen port = -1
SHD collect d talk port   = -1
SHD GW SERVICE            =
SHD MS SERVICE            =
SHD HOST                  =
SHD GW HOST               =
SHD STARTPATH             = /usr/sap/put/SRD/homeshd/SRD
SHD R3 START PROFILE      =
SHD PROFILE PATH          = /usr/sap/put/SRD/SYS/profile
SHD PROFILE NAME          =
SHD startsap              =
SHD stopsap               =
SHD workpath              =
SHD kernpath              = /usr/sap/put/exe
dba schema                = SAPR3
dba shd schema            = SAPR3SHD
connect env string        = dbs_ora_schema
REMOTE UPGRADE DIRECTORY =
SAP SERVICE ACCOUNT          =
SAP SERVICE ACCOUNT PWD= <NOT REPORTED>
Original shadow profile     =
..finished at 20080107083322 with status SUCCEEDED.
UPGRADEPHASE DBCHK_PRE
...started at 20080107083322
Condition level 1, total => FALSE '#if -52 >= 0' => FALSE
Condition level 1, total => FALSE '#if -52 >= 0' => FALSE
DB Environment for SAPup:
DBATYPE    ORACLE
DBAHOME    /oracle/SRD/102_64
DBAEXE     /oracle/SRD/102_64/bin
DBACONN    "SRD"
DBAVERS    10.2.0.2.0
KERNVERS   620
SAPVERS    620
DOKVERS    620
DBASUBTYPE STANDARD
DBAOPSYS   SAME_SYS
DBA2CONN   ""
COMPRELS   ""BBPCRM=400,PI_BASIS=2005_1_620,SAP_ABA=620,SAP_BASIS=620,ST-A/PI=01E_CRM400,ST-PI=2005_1_620""
Condition level 1, total => TRUE '#if 2 >= 0' => TRUE
DB Environment for SAPup:
DBATYPE    ORACLE
DBAHOME    /oracle/SRD/102_64
DBAEXE     /oracle/SRD/102_64/bin
DBACONN    "SRD"
DBAVERS    10.2.0.2.0
KERNVERS   620
SAPVERS    620
DOKVERS    620
DBASUBTYPE STANDARD
DBAOPSYS   SAME_SYS
DBA2CONN   ""
COMPRELS   ""BBPCRM=400,PI_BASIS=2005_1_620,SAP_ABA=620,SAP_BASIS=620,ST-A/PI=01E_CRM400,ST-PI=2005_1_620""
...begin dialogue at 20080107083324
...end dialogue at 20080107083419
Environment for SAPup:
SAPSID              = SRD
SAPHOST             = eux353
STARTPATH           = /usr/sap/SRD/SYS/exe/run
KERNPATH            = /usr/sap/SRD/SYS/exe/run
PROFPATH            = /usr/sap/SRD/SYS/profile
LOCAL SLOG          = /usr/sap/SRD/DVEBMGS40/log/SLOG40
LOCAL SLOG (OLD)    = /usr/sap/SRD/DVEBMGS40/log/SLOGO40
CENTRAL SLOG        = /usr/sap/SRD/SYS/global/SLOGJ
CENTRAL SLOG (OLD) = /usr/sap/SRD/SYS/global/SLOGJO
EPS INBOX           = /usr/sap/SRDtrans/EPS/in
EPS ROOT            = /usr/sap/SRDtrans/EPS
DBASID              = SRD
DBAHOST             = eux353
DBAPWD              = <NOT REPORTED>
NR R3TRANS          = 3
NR R3LOAD           = 1
IMPORT DESTTIME     = 86400
STARTR3             = "startsap"
STARTPARAMS R3      = "R3"
STOPR3              = "stopsap"
STOPPARAMS R3      = "R3"
STARTDB             = "startsap"
STARTPARAMS DB      = "DB"
STOPDB              = "stopsap"
STOPPARAMS DB      = "DB"
UPGRADE USER        = srdadm
UPGRADE LANGUAGE    = E
SLOGNAME            = SLOG700
ALOGNAME            = ALOG700
SYSNUM              = 40
PROFNAME            = /usr/sap/SRD/SYS/profile/SRD_DVEBMGS40_eux353
DDIC PWD            = <NOT REPORTED>
GATEWAY HOST        = eux353
GATEWAY SERVICE     = sapgw40
MS SERVICE          = 3640
SLOW SHADOW IMPORT = Y
MAX BUFREFTIME      = 120
BATCH HOST          = eux353
NR BTC-PROCS INTERN = 3
CUSTOMER GENERATION = 0
SAP START PROFILE   = START_DVEBMGS40_eux353
DEFPROFNAME         = /usr/sap/SRD/SYS/profile/DEFAULT.PFL
OSTYPE              = HP-UX IA64
OSVERS              = 11.23
DESTVERS            = 700
COMPDESTVERS        = PI_BASIS=2005_1_700,SAP_ABA=700,SAP_AP=700,SAP_BASIS=700,SAP_BW=700,SRM_PLUS=550,SRM_SERVER=550,ST-PI=2005_1_700
SUBSTSTVERS         = 700
COMPSUBSTSTVERS     = SAP_BASIS=700,SAP_ABA=700,SAP_BW=700,SRM_SERVER=550
DESTPRODSHORTID     = R/3
DESTPRODSHORTREL    = 700
IMPORT LANGUAGES    =
DB REPSWITCH PAR    = NOT_SPECIFIED
PARALLEL DDLNTABS   = 0
TABLSIZE            = 0
KERNEL BIT SELECTION = 64 bit, no choice
SHD INSTANCE NUMBER =
SHD send d talk port      = -1
SHD send d listen port    = -1
SHD collect d listen port = -1
SHD collect d talk port   = -1
SHD GW SERVICE            =
SHD MS SERVICE            =
SHD HOST                  =
SHD GW HOST               =
SHD STARTPATH             = /usr/sap/put/SRD/homeshd/SRD
SHD R3 START PROFILE      =
SHD PROFILE PATH          = /usr/sap/put/SRD/SYS/profile
SHD PROFILE NAME          =
SHD startsap              =
SHD stopsap               =
SHD workpath              =
SHD kernpath              = /usr/sap/put/exe
dba schema                = SAPR3
dba shd schema            = SAPR3SHD
connect env string        = dbs_ora_schema
REMOTE UPGRADE DIRECTORY =
SAP SERVICE ACCOUNT          =
SAP SERVICE ACCOUNT PWD= <NOT REPORTED>
Original shadow profile     =
NO UNICODE. DB factor is: 1
Phase log file: 'MCODCHK.LOG'
...begin dialogue at 20080107083419
...end dialogue at 20080107083430
Condition level 1, total => TRUE '#if 2 >= 0' => TRUE
..finished at 20080107083430 with status SUCCEEDED.
UPGRADEPHASE CONFCHK_IMP
...started at 20080107083430
Condition level 1, total => TRUE '#if 2 >= 0' => TRUE
Condition level 1, total => TRUE '#if 2 >= 0' => TRUE
DB Environment for SAPup:
DBATYPE    ORACLE
DBAHOME    /oracle/SRD/102_64
DBAEXE     /oracle/SRD/102_64/bin
DBACONN    "SRD"
DBAVERS    10.2.0.2.0
KERNVERS   620
SAPVERS    620
DOKVERS    620
DBASUBTYPE STANDARD
DBAOPSYS   SAME_SYS
DBA2CONN   ""
COMPRELS   ""BBPCRM=400,PI_BASIS=2005_1_620,SAP_ABA=620,SAP_BASIS=620,ST-A/PI=01E_CRM400,ST-PI=2005_1_620""
System configuration:
Operating system = HP-UX IA64
Version          = 11.23
Database type    = ORACLE
Version          = 10.2.0.2.0
..finished at 20080107083430 with status SUCCEEDED.
UPGRADEPHASE SOLMAN_CHK
...started at 20080107083430
...begin dialogue at 20080107083430
...end dialogue at 20080107083448
...begin dialogue at 20080107083448
...end dialogue at 20080107083641
..finished at 20080107083641 with status SUCCEEDED.
UPGRADEPHASE CHKSYSTYPE
...started at 20080107083641
Phase log file: 'CHKSYSTYPE.LOG'
System recognized: is not a final assembly system
..finished at 20080107083641 with status SUCCEEDED.
UPGRADEPHASE HIAV_CHK
...started at 20080107083641
Phase log file: 'HIAVCHK.LOG'
..finished at 20080107083641 with status SUCCEEDED.
UPGRADEPHASE J2EE_CHK1
...started at 20080107083641
Phase log file: 'J2EECHK.LOG'
...begin dialogue at 20080107083641
...end dialogue at 20080107083808
..finished at 20080107083808 with status SUCCEEDED.
UPGRADEPHASE REQ_J2EEUPG
...started at 20080107083808
Phase skipped due to condition 'J2EE_ONLY'
Skipping over to next phase, nothing to do for this system.
..finished at 20080107083808 with status SUCCEEDED.
UPGRADEPHASE SETSYNC_PREP_STARTED
...started at 20080107083808
Phase skipped due to condition 'J2EE_ONLY'
Skipping over to next phase, nothing to do for this system.
..finished at 20080107083808 with status SUCCEEDED.
UPGRADEPHASE REQ_READNOTE
...started at 20080107083808
Phase skipped due to condition 'CBU_only'
Skipping over to next phase, nothing to do for this system.
..finished at 20080107083808 with status SUCCEEDED.
UPGRADEPHASE INIT_CBU
...started at 20080107083808
Phase skipped due to condition 'CBU_only'
Skipping over to next phase, nothing to do for this system.
..finished at 20080107083808 with status SUCCEEDED.
UPGRADEPHASE CHECKGROUP_END0
...started at 20080107083808
Execution of PREPARE module Parameter input ends at 20080107083808
Execution of PREPARE module Initialization begins at 20080107083808
UPGRADEPHASE
UPGRADEPHASE INITCURENV
...started at 20080107083808
Environment for SAPup:
SAPSID              = SRD
SAPHOST             = eux353
STARTPATH           = /usr/sap/SRD/SYS/exe/run
KERNPATH            = /usr/sap/SRD/SYS/exe/run
PROFPATH            = /usr/sap/SRD/SYS/profile
LOCAL SLOG          = /usr/sap/SRD/DVEBMGS40/log/SLOG40
LOCAL SLOG (OLD)    = /usr/sap/SRD/DVEBMGS40/log/SLOGO40
CENTRAL SLOG        = /usr/sap/SRD/SYS/global/SLOGJ
CENTRAL SLOG (OLD) = /usr/sap/SRD/SYS/global/SLOGJO
EPS INBOX           = /usr/sap/SRDtrans/EPS/in
EPS ROOT            = /usr/sap/SRDtrans/EPS
DBASID              = SRD
DBAHOST             = eux353
DBAPWD              = <NOT REPORTED>
NR R3TRANS          = 3
NR R3LOAD           = 1
IMPORT DESTTIME     = 86400
STARTR3             = "startsap"
STARTPARAMS R3      = "R3"
STOPR3              = "stopsap"
STOPPARAMS R3      = "R3"
STARTDB             = "startsap"
STARTPARAMS DB      = "DB"
STOPDB              = "stopsap"
STOPPARAMS DB      = "DB"
UPGRADE USER        = srdadm
UPGRADE LANGUAGE    = E
SLOGNAME            = SLOG700
ALOGNAME            = ALOG700
SYSNUM              = 40
PROFNAME            = /usr/sap/SRD/SYS/profile/SRD_DVEBMGS40_eux353
DDIC PWD            = <NOT REPORTED>
GATEWAY HOST        = eux353
GATEWAY SERVICE     = sapgw40
MS SERVICE          = 3640
SLOW SHADOW IMPORT = Y
MAX BUFREFTIME      = 120
BATCH HOST          = eux353
NR BTC-PROCS INTERN = 3
CUSTOMER GENERATION = 0
SAP START PROFILE   = START_DVEBMGS40_eux353
DEFPROFNAME         = /usr/sap/SRD/SYS/profile/DEFAULT.PFL
OSTYPE              = HP-UX IA64
OSVERS              = 11.23
DESTVERS            = 700
COMPDESTVERS        = PI_BASIS=2005_1_700,SAP_ABA=700,SAP_AP=700,SAP_BASIS=700,SAP_BW=700,SRM_PLUS=550,SRM_SERVER=550,ST-PI=2005_1_700
SUBSTSTVERS         = 700
COMPSUBSTSTVERS     = SAP_BASIS=700,SAP_ABA=700,SAP_BW=700,SRM_SERVER=550
DESTPRODSHORTID     = R/3
DESTPRODSHORTREL    = 700
IMPORT LANGUAGES    =
DB REPSWITCH PAR    = NOT_SPECIFIED
PARALLEL DDLNTABS   = 0
TABLSIZE            = 0
KERNEL BIT SELECTION = 64 bit, no choice
SHD INSTANCE NUMBER =
SHD send d talk port      = -1
SHD send d listen port    = -1
SHD collect d listen port = -1
SHD collect d talk port   = -1
SHD GW SERVICE            =
SHD MS SERVICE            =
SHD HOST                  =
SHD GW HOST               =
SHD STARTPATH             = /usr/sap/put/SRD/homeshd/SRD
SHD R3 START PROFILE      =
SHD PROFILE PATH          = /usr/sap/put/SRD/SYS/profile
SHD PROFILE NAME          =
SHD startsap              =
SHD stopsap               =
SHD workpath              =
SHD kernpath              = /usr/sap/put/exe
dba schema                = SAPR3
dba shd schema            = SAPR3SHD
connect env string        = dbs_ora_schema
REMOTE UPGRADE DIRECTORY =
SAP SERVICE ACCOUNT          =
SAP SERVICE ACCOUNT PWD= <NOT REPORTED>
Original shadow profile     =
..finished at 20080107083808 with status SUCCEEDED.
UPGRADEPHASE DBCHK_INI
...started at 20080107083808
Condition level 1, total => TRUE '#if 2 >= 0' => TRUE
Condition level 1, total => TRUE '#if 2 >= 0' => TRUE
DB Environment for SAPup:
DBATYPE    ORACLE
DBAHOME    /oracle/SRD/102_64
DBAEXE     /oracle/SRD/102_64/bin
DBACONN    "SRD"
DBAVERS    10.2.0.2.0
KERNVERS   620
SAPVERS    620
DOKVERS    620
DBASUBTYPE STANDARD
DBAOPSYS   SAME_SYS
DBA2CONN   ""
COMPRELS   ""BBPCRM=400,PI_BASIS=2005_1_620,SAP_ABA=620,SAP_BASIS=620,ST-A/PI=01E_CRM400,ST-PI=2005_1_620""
Condition level 1, total => TRUE '#if 2 >= 0' => TRUE
DB Environment for SAPup:
DBATYPE    ORACLE
DBAHOME    /oracle/SRD/102_64
DBAEXE     /oracle/SRD/102_64/bin
DBACONN    "SRD"
DBAVERS    10.2.0.2.0
KERNVERS   620
SAPVERS    620
DOKVERS    620
DBASUBTYPE STANDARD
DBAOPSYS   SAME_SYS
DBA2CONN   ""
COMPRELS   ""BBPCRM=400,PI_BASIS=2005_1_620,SAP_ABA=620,SAP_BASIS=620,ST-A/PI=01E_CRM400,ST-PI=2005_1_620""
Environment for SAPup:
SAPSID              = SRD
SAPHOST             = eux353
STARTPATH           = /usr/sap/SRD/SYS/exe/run
KERNPATH            = /usr/sap/SRD/SYS/exe/run
PROFPATH            = /usr/sap/SRD/SYS/profile
LOCAL SLOG          = /usr/sap/SRD/DVEBMGS40/log/SLOG40
LOCAL SLOG (OLD)    = /usr/sap/SRD/DVEBMGS40/log/SLOGO40
CENTRAL SLOG        = /usr/sap/SRD/SYS/global/SLOGJ
CENTRAL SLOG (OLD) = /usr/sap/SRD/SYS/global/SLOGJO
EPS INBOX           = /usr/sap/SRDtrans/EPS/in
EPS ROOT            = /usr/sap/SRDtrans/EPS
DBASID              = SRD
DBAHOST             = eux353
DBAPWD              = <NOT REPORTED>
NR R3TRANS          = 3
NR R3LOAD           = 1
IMPORT DESTTIME     = 86400
STARTR3             = "startsap"
STARTPARAMS R3      = "R3"
STOPR3              = "stopsap"
STOPPARAMS R3      = "R3"
STARTDB             = "startsap"
STARTPARAMS DB      = "DB"
STOPDB              = "stopsap"
STOPPARAMS DB      = "DB"
UPGRADE USER        = srdadm
UPGRADE LANGUAGE    = E
SLOGNAME            = SLOG700
ALOGNAME            = ALOG700
SYSNUM              = 40
PROFNAME            = /usr/sap/SRD/SYS/profile/SRD_DVEBMGS40_eux353
DDIC PWD            = <NOT REPORTED>
GATEWAY HOST        = eux353
GATEWAY SERVICE     = sapgw40
MS SERVICE          = 3640
SLOW SHADOW IMPORT = Y
MAX BUFREFTIME      = 120
BATCH HOST          = eux353
NR BTC-PROCS INTERN = 3
CUSTOMER GENERATION = 0
SAP START PROFILE   = START_DVEBMGS40_eux353
DEFPROFNAME         = /usr/sap/SRD/SYS/profile/DEFAULT.PFL
OSTYPE              = HP-UX IA64
OSVERS              = 11.23
DESTVERS            = 700
COMPDESTVERS        = PI_BASIS=2005_1_700,SAP_ABA=700,SAP_AP=700,SAP_BASIS=700,SAP_BW=700,SRM_PLUS=550,SRM_SERVER=550,ST-PI=2005_1_700
SUBSTSTVERS         = 700
COMPSUBSTSTVERS     = SAP_BASIS=700,SAP_ABA=700,SAP_BW=700,SRM_SERVER=550
DESTPRODSHORTID     = R/3
DESTPRODSHORTREL    = 700
IMPORT LANGUAGES    =
DB REPSWITCH PAR    = NOT_SPECIFIED
PARALLEL DDLNTABS   = 0
TABLSIZE            = 0
KERNEL BIT SELECTION = 64 bit, no choice
SHD INSTANCE NUMBER =
SHD send d talk port      = -1
SHD send d listen port    = -1
SHD collect d listen port = -1
SHD collect d talk port   = -1
SHD GW SERVICE            =
SHD MS SERVICE            =
SHD HOST                  =
SHD GW HOST               =
SHD STARTPATH             = /usr/sap/put/SRD/homeshd/SRD
SHD R3 START PROFILE      =
SHD PROFILE PATH          = /usr/sap/put/SRD/SYS/profile
SHD PROFILE NAME          =
SHD startsap              =
SHD stopsap               =
SHD workpath              =
SHD kernpath              = /usr/sap/put/exe
dba schema                = SAPR3
dba shd schema            = SAPR3SHD
connect env string        = dbs_ora_schema
REMOTE UPGRADE DIRECTORY =
SAP SERVICE ACCOUNT          =
SAP SERVICE ACCOUNT PWD= <NOT REPORTED>
Original shadow profile     =
NO UNICODE. DB factor is: 1
Condition level 1, total => TRUE '#if 2 >= 0' => TRUE
..finished at 20080107083808 with status SUCCEEDED.
UPGRADEPHASE RFCCHK_INI
...started at 20080107083808
Phase log file: 'RFCCHK_INI.LOG'
..finished at 20080107083810 with status SUCCEEDED.
UPGRADEPHASE VERSCHK_INI
...started at 20080107083810
Phase list derived in VERSCHK:
INITCURENV
DBCHK_INI
RFCCHK_INI
VERSCHK_INI
VALCHK_INI
TOOLVERSION_INI
UNICODE_CHK_PRE
TOOLVERSION_UPG1
DBCONNCHK_INI
SETSYNC_INFO_FINISHED
UCMIG_DECISION
CLNT_CHK_INI
PATCH_CHK1
INTCHK_INI
ADJ_CNTRANS
INIT_CNTRANS
CNTRANS_PRE
DMPSPC_INI
JOB_RSDB4090
CHK_DB6_REG_PRE
CHK_DB6_PAR_INI
SPACECHK_INI
KRNCHK_DEST
DBPREP_CHK
EXECCV
EXECAV
COMPINFO_INI
ADDON_CHK
ADDON_INFO
ADDON_SPEC1
ADDON_TREAS
ADDON_WFM
ADDON_DMC
ACE_CHK
CRM_BILL
PR_DBPAR
CHECKGROUP_END1
..finished at 20080107083810 with status SUCCEEDED.
UPGRADEPHASE VALCHK_INI
...started at 20080107083810
Phase log file: 'VALCHK.LOG'
..finished at 20080107083810 with status SUCCEEDED.
UPGRADEPHASE TOOLVERSION_INI
...started at 20080107083810
Phase log file: 'TOOLVERS.LOG'
TOOL-VERSION 'disp+work': SYS_DISPWORK_REL = '640'
TOOL-VERSION 'disp+work': SYS_DISPWORK_VARIANT = '640_REL'
TOOL-VERSION 'disp+work': SYS_DISPWORK_64BIT = 'ON'
TOOL-VERSION 'disp+work': SYS_DISPWORK_DATE = 'Dec 3 2007 20:15:49'
TOOL-VERSION 'disp+work': SYS_DISPWORK_PATCHNUM = '211'
TOOL-VERSION 'tp': SYS_TP_VERSION = '340.16.38'
TOOL-VERSION 'tp': SYS_TP_REL = '640'
TOOL-VERSION 'tp': SYS_TP_PATCHNUM = '209'
TOOL-VERSION 'R3trans': SYS_R3TRANS_VERSION = '6.13'
TOOL-VERSION 'R3trans': SYS_R3TRANS_REL = '640'
TOOL-VERSION 'R3trans': SYS_R3TRANS_DATE = '10.07.07'
TOOL-VERSION 'R3trans': SYS_R3TRANS_PATCHNUM = '192'
TOOL-VERSION 'R3load': SYS_R3LOAD_REL = '6.40'
TOOL-VERSION 'R3load': SYS_R3LOAD_VERSION = '1.4'
Environment for SAPup:
SAPSID              = SRD
SAPHOST             = eux353
STARTPATH           = /usr/sap/SRD/SYS/exe/run
KERNPATH            = /usr/sap/SRD/SYS/exe/run
PROFPATH            = /usr/sap/SRD/SYS/profile
LOCAL SLOG          = /usr/sap/SRD/DVEBMGS40/log/SLOG40
LOCAL SLOG (OLD)    = /usr/sap/SRD/DVEBMGS40/log/SLOGO40
CENTRAL SLOG        = /usr/sap/SRD/SYS/global/SLOGJ
CENTRAL SLOG (OLD) = /usr/sap/SRD/SYS/global/SLOGJO
EPS INBOX           = /usr/sap/SRDtrans/EPS/in
EPS ROOT            = /usr/sap/SRDtrans/EPS
DBASID              = SRD
DBAHOST             = eux353
DBAPWD              = <NOT REPORTED>
NR R3TRANS          = 3
NR R3LOAD           = 1
IMPORT DESTTIME     = 86400
STARTR3             = "startsap"
STARTPARAMS R3      = "R3"
STOPR3              = "stopsap"
STOPPARAMS R3      = "R3"
STARTDB             = "startsap"
STARTPARAMS DB      = "DB"
STOPDB              = "stopsap"
STOPPARAMS DB      = "DB"
UPGRADE USER        = srdadm
UPGRADE LANGUAGE    = E
SLOGNAME            = SLOG700
ALOGNAME            = ALOG700
SYSNUM              = 40
PROFNAME            = /usr/sap/SRD/SYS/profile/SRD_DVEBMGS40_eux353
DDIC PWD            = <NOT REPORTED>
GATEWAY HOST        = eux353
GATEWAY SERVICE     = sapgw40
MS SERVICE          = 3640
SLOW SHADOW IMPORT = Y
MAX BUFREFTIME      = 120
BATCH HOST          = eux353
NR BTC-PROCS INTERN = 3
CUSTOMER GENERATION = 0
SAP START PROFILE   = START_DVEBMGS40_eux353
DEFPROFNAME         = /usr/sap/SRD/SYS/profile/DEFAULT.PFL
OSTYPE              = HP-UX IA64
OSVERS              = 11.23
DESTVERS            = 700
COMPDESTVERS        = PI_BASIS=2005_1_700,SAP_ABA=700,SAP_AP=700,SAP_BASIS=700,SAP_BW=700,SRM_PLUS=550,SRM_SERVER=550,ST-PI=2005_1_700
SUBSTSTVERS         = 700
COMPSUBSTSTVERS     = SAP_BASIS=700,SAP_ABA=700,SAP_BW=700,SRM_SERVER=550
DESTPRODSHORTID     = R/3
DESTPRODSHORTREL    = 700
IMPORT LANGUAGES    =
DB REPSWITCH PAR    = NOT_SPECIFIED
PARALLEL DDLNTABS   = 0
TABLSIZE            = 0
KERNEL BIT SELECTION = 64 bit, no choice
SHD INSTANCE NUMBER =
SHD send d talk port      = -1
SHD send d listen port    = -1
SHD collect d listen port = -1
SHD collect d talk port   = -1
SHD GW SERVICE            =
SHD MS SERVICE            =
SHD HOST                  =
SHD GW HOST               =
SHD STARTPATH             = /usr/sap/put/SRD/homeshd/SRD
SHD R3 START PROFILE      =
SHD PROFILE PATH          = /usr/sap/put/SRD/SYS/profile
SHD PROFILE NAME          =
SHD startsap              =
SHD stopsap               =
SHD workpath              =
SHD kernpath              = /usr/sap/put/exe
dba schema                = SAPR3
dba shd schema            = SAPR3SHD
connect env string        = dbs_ora_schema
REMOTE UPGRADE DIRECTORY =
SAP SERVICE ACCOUNT          =
SAP SERVICE ACCOUNT PWD= <NOT REPORTED>
Original shadow profile     =
Condition level 1, total => FALSE '#if 2 < 0' => FALSE
Condition level 1, total => FALSE '#elseif 2 < 0' => FALSE
Condition level 2, total => FALSE '#if "ORACLE" == "SAPDB"' => FALSE
Condition level 1, total => FALSE '

Is the system still doing something? Check with "top" on operating system level (maybe archiver stuck?)
Also step to
/usr/sap/put/log
/usr/sap/put/tmp
and issue an "ls -lt | more" to check the latest logfiles.
Markus

Data Guard - MRP stuck issues on a physical standby database

Hi,
Oracle 11.2.0.3 DG running. When i do a switchover the physical standby database has error with following error
ARC0: LGWR is actively archiving destination LOG_ARCHIVE_DEST_2
ARCH: Archival stopped, error occurred. Will continue retrying
ORACLE Instance <primaryDB> - Archival Error
On standby DB
SQL>select process, thread#, sequence#, status from v$managed_standby where process='MRP0';
PROCESS THREAD# SEQUENCE# STATUS
MRP0 1 548 APPLYING_LOG
So according to Oracle support link i executed following
SQL>recover managed standby database cancel;
SQL>recover automatic standby database;
The above seems to resolve the issue. What is causing is this?

Hello again;
Those both look perfect. I combed through my notes and found nothing like this for your version.
Yes, I would open an SR since it appears you have done everything correct.
ORA-600 [3020] "Stuck Recovery" [ID 30866.1]
The "Known Bugs" section of the above has a few 11.2.0.3 entries.
Generally the MRP gets stuck because data Guard thinks there's a GAP, you run out of room in the FRA on the Standby, or redo logs are too small and the system is switching very fast.
Best Regards
mseberg
Later
Never asked you but this "log_archive_max_processes" can be set as high as 30.
Edited by: mseberg on Jul 16, 2012 8:01 PM
h2. Still later
Found this which is closer :
Bug 13553883 - Archiver stuck but no ORA-19xxx error in alert log (messages need changing) [ID 13553883.8]

Brarchive - BR0301W - ORA-00257: archiver error

Hi all,
when calling /usr/sap/B16/SYS/exe/run/brarchive -u / -p initB16.sap -d rman_util -sd and there already is an archiver stuck I get the following error:
BR0002I BRARCHIVE 7.20 (16)
BR0006I Start of offline redolog processing: aehmrvjb.svd 2011-12-23 09.41.11
BR0484I BRARCHIVE log file: /oracle/B16/saparch/aehmrvjb.svd
BR0280I BRARCHIVE time stamp: 2011-12-23 09.41.11
BR0301W SQL error -257 at location BrDbConnect-2, SQL statement:
'CONNECT /'
ORA-00257: archiver error. Connect internal only, until freed.
brarchive tries to create a pfile from the spfile before calls rman to archive the offline log files.
I assume, that this is done by calling sqlplus with 'CONNECT /'' which fails because connecting as sysdba is necessary in this situation.
Any suggestions how to circumvent this, so that the above error message doesn't show up?
The problem doesen't seem to be critical because brarchive still is able to call RMAN successfully and by this the archiver stuck is resolved. It would be better, though, if brarchive doesn't run into any errors at all.
Thanks for your support.
Best Rgs,
Thorsten

Hi there,
just to clarify: brarchive has no problem to archive the offline redologs themselves:
The problem doesen't seem to be critical because brarchive still is able to call RMAN successfully and by this the archiver stuck is resolved. It would be better, though, if brarchive doesn't run into any errors at all.
The actual problem is, that brarchive tries to create a pfile from the spfile via a sqlplus call and it tries to do this by "connect /" without the sysdba option. This behavior results in the error message I posted.
What I'd actualy like to know if there's any way to explicitly tell brarchive to connect with the sysdba option?
Best Rgs,
Thorsten

DRS archive log

Hi,
I have currently set two places to store my offline archive log. The configuration in oracle as below:
LOG_ARCHIVE_DEST_1 LOCATION=U:\oracle\SID\oraarch\SIDarch
LOG_ARCHIVE_DEST_2 SERVICE=SID_DR
LOG_ARCHIVE_DEST_2 is pointing to our DRS server connected thru network.
My questions:
1- If there is a problem/failure on the network, what will happen for LOG_ARCHIVE_DEST_2? Will my primary database hangs due to this kind of configuration?
2- What will happen if destination 2, the filesystem is full? Will I get the archive stuck problem?
3- Is there any other setback configuring this way?
Thanks in advance
Best Regards.

I'm getting this kind of error in my oracle trace file. Also, all the WP are hanging and nothing is being process. What is the cause of this? Is this something to LOG_ARCHIVE_DEST_2?
Line: -
Dump file r:\oracle\epf\saptrace\background\epf_arc0_5660.trc
Sun Aug 09 07:18:28 2009
ORACLE V9.2.0.8.0 - Production vsnsta=0
vsnsql=12 vsnxtr=3
Windows 2000 Version 5.2 Service Pack 2, CPU type 586
Oracle9i Enterprise Edition Release 9.2.0.8.0 - Production
With the Partitioning, OLAP and Oracle Data Mining options
JServer Release 9.2.0.8.0 - Production
Windows 2000 Version 5.2 Service Pack 2, CPU type 586
Instance name: epf
Redo thread mounted by this instance: 0 <none>
Oracle process number: 8
Windows thread id: 5660, image: ORACLE.EXE
SESSION ID:(7.1) 2009-08-09 07:18:28.140
Destination LOG_ARCHIVE_DEST_2 is in CLUSTER CONSISTENT mode
Destination LOG_ARCHIVE_DEST_2 is in CLUSTER CONSISTENT mode
Destination LOG_ARCHIVE_DEST_2 is in MAXIMUM PERFORMANCE mode
Destination LOG_ARCHIVE_DEST_2 is in CLUSTER CONSISTENT mode
Destination LOG_ARCHIVE_DEST_2 is in MAXIMUM PERFORMANCE mode
2009-08-09 08:00:00.021
RFS network connection lost at host 'EPF_DR'
Error 3114 writing standby archive log file at host 'EPF_DR'
2009-08-09 08:00:00.021 51426 kcrr.c
ARC0: I/O error 3114 archiving log 2 to 'EPF_DR'
2009-08-09 08:00:00.037
kcrrfail: dest:2 err:3114 force:0
Local destination LOG_ARCHIVE_DEST_1 is still active
ORA-03114: not connected to ORACLE
2009-08-09 08:05:12.347
Error 12537 connecting to destination LOG_ARCHIVE_DEST_2 standby host 'EPF_DR'
Error 12537 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'EPF_DR'
2009-08-09 08:05:12.347 51426 kcrr.c
ARC0: Error 12537 Creating archive log file to 'EPF_DR'
2009-08-09 08:05:12.347
kcrrfail: dest:2 err:12537 force:0
ORA-12537: TNS:connection closed
Error 16058 attaching RFS server to standby instance at host 'EPF_DR'
Error 16058 attaching to destination LOG_ARCHIVE_DEST_2 standby host 'EPF_DR'
2009-08-09 08:26:40.411 51426 kcrr.c
ARC0: Error 16058 Creating archive log file to 'EPF_DR'
2009-08-09 08:26:40.411
kcrrfail: dest:2 err:16058 force:0
ORA-16058: standby database instance is not mounted
Standby database restarted; old mount ID 0xe69bf2de now 0xe6e833df
Destination LOG_ARCHIVE_DEST_2 is in CLUSTER CONSISTENT mode
Destination LOG_ARCHIVE_DEST_2 is in MAXIMUM PERFORMANCE mode
Destination LOG_ARCHIVE_DEST_2 is in CLUSTER CONSISTENT mode
Destination LOG_ARCHIVE_DEST_2 is in MAXIMUM PERFORMANCE mode
Destination LOG_ARCHIVE_DEST_2 is in CLUSTER CONSISTENT mode
Destination LOG_ARCHIVE_DEST_2 is in MAXIMUM PERFORMANCE mode
Destination LOG_ARCHIVE_DEST_2 is in CLUSTER CONSISTENT mode
Destination LOG_ARCHIVE_DEST_2 is in MAXIMUM PERFORMANCE mode
Destination LOG_ARCHIVE_DEST_2 is in CLUSTER CONSISTENT mode
Destination LOG_ARCHIVE_DEST_2 is in MAXIMUM PERFORMANCE mode
Destination LOG_ARCHIVE_DEST_2 is in CLUSTER CONSISTENT mode
Edited by: Eida Hanafiah on Aug 21, 2009 8:12 AM
Edited by: Eida Hanafiah on Aug 21, 2009 8:14 AM

Snapshot Backups on HP EVA SAN

Hi everyone,
We are implementing a new HP EVA SAN for our SAP MaxDB Wintel environment. As part of the SAN setup we will be utilising the EVAs snapshot technology to perform a nightly backup.
Currently HP Data Protector does not support MaxDB for its "Zero Downtime Backup" concept (ZDB), thus we need to perform LUN snapshots using the EVAs native commands. ZDB would have been nice as it integrates into SAP and lets the DB/SAP know when a snapshot backup has occurred. However as I mentioned this feature is not available on MaxDB (only SAP on Oracle).
We are aware that SAP supports snapshots on external storage devices as stated in OSS notes 371247 and 616814.
To perform the snapshot we would do something similar (if not exactly) like note 616814 describes as below:
To create the split mirror or snapshot, proceed as follows:
             dbmcli -d <database_name> -u < dbm_user>,<password>
                  util_connect < dbm_user>,<password>
                  util_execute suspend logwriter
               ==> Create the snapshot on the EVA
                  util_execute resume logwriter
                  util_release
                  exit
Obviously MaxDB and SAP are unaware that a "backup" has been performed. This poses a couple of issues that I would like to see if anyone has a solution too.
a. To enable automatic log backup MaxDB must know that it has first completed a "full" backup. Is it possible to have MaxDB be aware that a snapshot backup has been taken of the database, thus allowing us to enable automatic log backup?
b. SAP also likes to know its been backed up also. Earlywatch Alert reports start to get a little upset when you don't perform a backup on the system for awhile.
Also DB12 will mention that the system isn't in a recoverable state, when in fact it is. Any work arounds available here?
Cheers
Shaun

Hi Shaun,
interesting thread sofar...
> It would be nice to see HP and SAP(MaxDB) take the snapshot technology one or two steps further, to provide a guaranteed consistent backup, and can be block level verified. I think HPs ZDB (zero downtime backup eg snapshots) technology for SAP on Oracle using Data Protector does this now?!??!
Hmm... I guess the keyword here is 'market'. If there is enough market potential visible, I tend to believe that both SAP and HP would happily try to deliver such tight integration.
I don't know how this ZDB stuff works with Oracle, but how could the HP software possibly know how a Oracle block should look like?
No, there are just these options to actually check for block consistency in Oracle: use RMAN, use DBV or use SQL to actually read your data (via EXP, EXPDB, ANALYZE, custom SQL)
Even worse, you might come across block corruptions that are not covered by these checks really.
> Data corruption can mean so many things. If your talking structure corruption or block corruption, then you do hope that your consistency checks and database backup block checks will bring this to the attention of the DBA. Hopefully recovery of the DB from tape and rolling forward would resolve this.
Yes, I was talking about data block corruption. Why? Because there is no reliable way to actually perform a semantic check of your data. None.
We (SAP) simply rely on that, whatever we write to the database by the Updater is consistent from application point of view.
Having handled far too much remote consulting messages concerning data rescue due to block corruptions I can say: getting all readable data from the corrupt database objects is really the easy part of it.
The problems begin to get big, once the application developers need to think of reports to check and repair consistency from application level.
> However if your talking data corruption as is "crap data" has been loaded into the database, or a rogue ABAP has corrupted several million rows of data then this becomes a little more tricky. If the issue is identified immediately, restoring from backup is a fesible option for us.
> If the issue happened over 48hrs ago, then restoring from a backup is not an option. We are a 24x7x365 manufacturing operation. Shipping goods all around the world. We produce and ship to much product in a 24hr window that can not be rekeyed (or so the business says) if the data is lost.
Well in that case you're doomed. Plain and simple. Don't put any effort into getting "tricky", just let never ever run any piece of code that had not passed the whole testfactory. That's really the only chance.
> We would have to get tricky and do things such as restore a copy of the production database to another server, and extract the original "good" documents from the copy back into the original, or hopefully the rogue ABAP can correct whatever mistake they originally made to the data.
That's not a recovery plan - that is praying for mercy.
I know quite a few customer systems that went to this "solution" and had inconsistencies in their system for a long long time afterwards.
> Look...there are hundreds of corruption scenarios we could talk about, but each issue will have to be evaluated, and the decision to restore or not would be decided based on the issue at hand.
I totally agree.
The only thing that must not happen is: open a callconference and talk about what a corruption is in the first place, why it happened, how it could happen at all ... I spend hours of precious lifetime in such non-sense call confs, only to see - there is no plan for this at customer side.
> I would love to think that this is something we could do daily to a sandpit system, but with a 1.7TB production database, our backups take 6hrs, a restore would take about 10hrs, and the consistency check ... well a while.
We have customers saving multi-TB databases in far less time - it is possible.
> And what a luxury to be able to do this ... do you actually know of ANY sites that do this?
Quick Backups? Yes, quite a few. Complete Backup, Restore, Consistency Check cycle? None.
So why is that? I believe it's because there is no single button for it.
It's not integrated into the CCMS and/or the database management software.
It might also be (hopefully) that I never hear of these customers. See as a DB Support Consultant I don't get in touch with "sucess stories". I see failures and bugs all day.
To me the correct behaviour would be to actually stop the database once the last verified backup is too old. Just like everybody is used to it, when he hits a LOGFULL /ARCHIVER STUCK situation.
Until then - I guess I will have a lot more data rescue to do...
> Had a read ... being from New Zealand I could easily relate to the sheep =)
> Thats not wan't I meant. Like I said we are a 24x7x365 system. We get a maximum of 2hrs downtime for maintenance a month. Not that we need it these days as the systems practically run themselves. What I meant was that between 7am and 7pm are our busiest peak hours, but we have dispatch personnel, warehouse operations, shift supervisors ..etc.. as well as a huge amount of batch running through the "night" (and day). We try to maintain a good dialog response during the core hours, and then try to perform all the "other" stuff around these hours, including backups, opt stats, and business batch, large BI extractions ..etc..
> Are we busy all day and night ... yes ... very.
Ah ok - got it!
Especially in such situations I would not try to implement consistency checks on your prod. database.
Basically running a CHECK DATA there does not mean anything. Right after a table finished the check it can get corrupted although the check is still running on other tables. So you have no guranteed consistent state in a running database - never really.
On the other hand, what you really want to know is not: "Are there any corruptions in the database?" but "If there would be any corruptions in the database, could I get my data back?".
This later question can only be answered by checking the backups.
> Noted and agreed. Will do daily backups via MaxDB kernel, and a full verification each week.
One more customer on the bright side
> One last question. If we "restored" from an EVA snapshot, and had the DB logs upto the current point-in-time, can you tell MaxDB just to roll forward using these logs even though a restore wasn't initiated via MaxDB?
I don't see a reason why not - if you restore the data and logarea and bring the db to admin mode than it uses the last successfull savepoint for startup.
If you than use recover_start to supply more logs that should work.
But as always this is something that needs to be checked on your system.
That has been a really nice discussion - hope you don't get my comments as offending, they really aren't meant that way.
KR Lars

Note 1054131 - Invalid DB objects after upgrade

HI,
We performed a migration from SAP 4.6C/Oracle9i.solaris to SAP 4.6C/Oracle10g/HPUX.
Now we need to upgrade SAP4.6C/Oracle10g/HPUX to ECC6.0.
As a prerequisite, I have checked the note
Note 1054131 - Invalid DB objects after upgrade
And I ran the script
SQL> SELECT OWNER, OBJECT_NAME, OBJECT_TYPE FROM DBA_OBJECTS
2 WHERE STATUS='INVALID'
3 AND
4 OWNER='SYS';
OWNER
OBJECT_NAME
OBJECT_TYPE         STATUS
SYS
DBMS_REPCAT_FLA
PACKAGE BODY        INVALID
SYS
DBMS_REPCAT_MAS
PACKAGE BODY        INVALID
OWNER
OBJECT_NAME
OBJECT_TYPE         STATUS
SYS
DBMS_REPCAT_UTL2
PACKAGE BODY        INVALID
SYS
DBMS_REDEFINITION
OWNER
OBJECT_NAME
OBJECT_TYPE         STATUS
PACKAGE BODY        INVALID
All the invalid objects are package body, can anyone help me how to proceed with this, can I proceed my upgrade to ECC 6.0 or do I need to delete the package body.
If I want to delete the package body,can you pl give me the commands and also post which whether I need to execute any steps
Pl help
Thanks
Senthil

Hi,
I guess you are talking about the Oracle Upgrade and not ECC Upgrade, as following are the pre-requisites for an ECC upgrade.
Making Database-Specific Preparations for Oracle
1. Check the value of parameter shared_pool_size:
4 Preparation
Making Preparations at the Database Level
Oracle 9.2: Check the value in file $ORACLE_HOME/dbs/init<SID>.ora.
Oracle 10.1 and higher:
select NAME, VALUE from v$parameter where name=shared_pool_size;
select NAME, VALUE from v$parameter where name=shared_pool_reserved_size;
If the value is lower than 150 MB, increase it to at least 150 MB (400 MB is better), and restart the
database.
2. Log on as user <sapsid>adm at the operating system level.
3. Log on to the database as the Oracle user system with sqlplus
4. Check the resource quotas of the database user SAPR3 or SAP<SAPSID>:
Oracle error 1536 can occur during the upgrade if the resource quotas of database user SAPR3
orSAP<SAPSID> are limited. Make sure that these quotas are unlimited. Check whether the table
DBA_SYS_PRIVS contains one of the following entries:
grantee=SAPR3/SAP<SAPSID>,privilege=UNLIMITED TABLESPACE,adm=YES
grantee=SAPR3/SAP<SAPSID>,privilege=UNLIMITED TABLESPACE,adm=NO
To do this, enter the following SQLPLUS statement:
select * from dba_sys_privs where grantee = SAPR3/SAP<SAPSID>;
If this entry does not exist, enter the SQLPLUS statement:
grant unlimited tablespace to sapr3/SAP<SAPSID>;
5. Log off from the database with the command quit.
6. Only if using the dictionary managed tablespaces function:
Make sure that the storage parameters MAXEXTENTS and NEXT have the correct values for certain tables and indexes. Otherwise, they may overflow during the upgrade. The Oracle-specific upgrade SAP Note contains the tables and the required minimum values.You can display the current settings with BRSPACE. The index names are not constant. However, you can also determine these names with BRSPACE. SAP Note 11777 describes how to change the parameters NEXT and MAXEXTENTS.
7. Only valid for: SAP R/3 3.1I
Make sure that parameter OPTIMIZER_MODE is set to OPTIMIZER_MODE=RULE.
For Oracle 9.2, check and, if necessary, edit the following Oracle profile:
$ORACLE_HOME/dbs/init<SAPSID>.ora
For Oracle 10.1. and higher, use the following statements:
Sqlplus /nolog
Connect /as sysdba
Alter system set OPTIMIZER_MODE=RULE scope=spfile;
8. Only if you do not switch off archiving during the upgrade:
If you want to leave brarchive running during the upgrade to avoid archiver stuck situations (brarchive -f ...), proceed as follows:
a) Create a temporary copy of brarchive:
4 Preparation
4.23 Making Preparations at the SAP System Level
cp /usr/sap/<SAPSID>/SYS/exe/run/brarchive /tmp
b) Start brarchive as user ora<sapsid> from the temporary directory /tmp/brarchive -f ...
c) After the upgrade, delete the copy of brarchive.
This procedure avoids upgrade errors caused by the program files being overwritten during the upgrade.
9. If your database version is already higher than the minimum version for the new release, we recommend that you exchange the DBA tools (such as BRSPACE) for the upgrade. The Database Software Oracle DVD for the database contains the up-to-date tools that you unpacked on the current kernel when you migrated the database. After you execute PREPARE, unpack this archive again into the exe subdirectory of the upgrade directory. This overwrites the DBA tools optimized for the minimum required database version with the tools best suited to your database version.
And if you are talking about an Oracle Upgrade then you just need these to compare once you have upgraded to 10g.
3.9 Checking for Invalid Database Objects
This optional step lets you check if there are any invalid database objects before the database upgrade to Oracle database 10g starts. After the upgrade it helps you distinguish database objects that have become invalid due to the upgrade process from those that were already invalid to start with.
Procedure
1. Execute the following commands:
SQL> spool invalid_objects
SQL> select unique object_name, object_type, owner from dba_objects where status
= 'INVALID';
SQL> @?/rdbms/admin/utlrp.sql
SQL> select unique object_name, object_type, owner from dba_objects where status
= 'INVALID';
SQL> spool off
A list of invalid objects before the upgrade is now generated.
2. Check the list of invalid objects after the upgrade.
If any objects in the list from before the upgrade are also in the list of invalid objects after the upgrade, you can be sure that this is not due to the upgrade process.
Regards,
Suhas

ABAP/4 run time error with error code SNAP_NO_NEW_ENTRY

Dear All,
I've installed SAP R/3 IDES on Oracle on Windows 2003 server.After clicking Log on button , I should be asked to enter client,user and password.But, my system does not display such details.Instead I get ABAP/4 run time error with error code SNAP_NO_NEW_ENTRY that too after a long time.
Can you please address what is the reason for this problem and how to over ride it?
Regards,
S.Suresh

Hi,
the most probable reason is an archiver stuck. Backup the archived redo log files and delete them afterwards.
The database will archive some more logs after this. Handle them in the same manor. For complete explanation search for brtools.
Regards
Ralph Ganszky

Backup failure

hi all,
while taking the backup of my solution manager (Full database online backup and redo log files) through DB13 following error occured and the backup failed.however i am able to take backup from BRTOOLS and just full database online backup.can anyone please help me out in this issue.i am getting the following in detail log list:
BR0002I BRARCHIVE 7.00 (33)
BR0006I Start of offline redo log processing: aeagywve.dsv 2009-04-04 16.20.06
BR0484I BRARCHIVE log file: D:\oracle\SMS\saparch\aeagywve.dsv
BR0477I Oracle pfile E:\oracle\SMS\102\database\initSMS.ora created from spfile E:\oracle\SMS\102\database\spfileSMS.ora
BR0101I Parameters
Name                           Value
oracle_sid                     SMS
oracle_home                    E:\oracle\SMS\102
oracle_profile                 E:\oracle\SMS\102\database\initSMS.ora
sapdata_home                   D:\oracle\SMS
sap_profile                    E:\oracle\SMS\102\database\initsms.sap
backup_dev_type                disk
archive_dupl_del               only
system_info                    SAPServiceSMS SMSANDBOX01 Windows 5.2 Build 3790 Service Pack 2 Intel
oracle_info                    SMS 10.2.0.2.0 8192 541 72059160 SMSANDBOX01 UTF8 UTF8
sap_info                       700 SAPSR3 0002LK0003SMS0011B13383093760013NetWeaver_ORA
make_info                      NTintel OCI_10201_SHARE May 6 2008
command_line                   brarchive -u / -jid LOG__20090404162005 -c force -p initsms.sap -ds
BR0013W No offline redo log files found for processing
BR0007I End of offline redo log processing: aeagywve.dsv 2009-04-04 16.20.07
BR0280I BRARCHIVE time stamp: 2009-04-04 16.20.07
BR0004I BRARCHIVE completed successfully with warnings
thanx a lot

Hi,
Are the redo logs you see at OS level, recently generated? these may be old archive logs may be during a recovery time... please cross check.
if they are recent - please check if only archive log backup is running successfully or not (otherwise you may encounter archiver stuck situation)
Regards,
Debasis

Problem with starting SAP Database ..

Hi,
I have a issue with starting the DB. the detailed log is attached below.
When I had a Performance issue, I had tried to stop the SAP instance and the DB.
But thats not stopped. So I have restarted the OS.
After restarting the OS the DB is not comming up.
Its throwing the following log
SQL*Plus: Release 10.2.0.4.0 - Production on Sat Nov 15 13:11:16 2008
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
Connected to an idle instance.
ORACLE instance started.
Total System Global Area 2365587456 bytes
Fixed Size                  2057952 bytes
Variable Size            1191184672 bytes
Database Buffers         1157627904 bytes
Redo Buffers               14716928 bytes
Database mounted.
ORA-16038: log 4 sequence# 3468 cannot be archived
ORA-19502: write error on file "", blockno (blocksize=)
ORA-00312: online log 4 thread 1: '/oracle/TRQ/origlogB/log_g14m1.dbf'
ORA-00312: online log 4 thread 1: '/oracle/TRQ/mirrlogB/log_g14m2.dbf'
Please give me an solution to solve this issue.
Thanx & Regards,
Kumar

>ORA-16038: log 4 sequence# 3468 cannot be archived
the problem is your archive directory is full. take archive log backup or move old archive log files to another location.
follow Note 391 - Archiver stuck
Cheers,
-Sunil

ABAP/4 runtime error SNAP_NO_NEW_ENTRY

Hi All,
I am unable to login in to my SAP server, after entering user id and password, the below ABAP Dump is displayed
ABAP/4 runtime error SNAP_NO_NEW_ENTRY
I have checked the SAP notes, but no luck
Please advise
SAPXPT

Hello,
SAP note 17537 describes the following :
The error may be caused by the following:
- Table SNAP is full,
- short dump was not written due to database problems,
- short dump has already been solved by reorganization.
So check if the SNAP table is full or if there is a general database problem.
Probably it is the last one, maybe a connection problem to the DB, archiver stuck, ...
Can you still connect to the database with the command : R3trans -d
Merry Christmas,
Wim Van den Wyngaert

System Busy and unable to login

Please explain the proceduce to solve this issue and areas to check.....give me general idea for this question ...i am using 4.7 ides

perhaps one of your hard disk is full? if so, check for archiving stuck.

Applemobilesync.exe not running during restore

Hi all,
After trying to update my iOS 4 iPhone 3GS to iOS 5 there were a lot of problems, so I had to restore my phone with a clean iOS5 ipsw, then whenever I try and restore my phone from the iTunes backup, I get a message saying that the backup session failed.
Upon closer inspection, I have realised that the AppleMobileSync.exe process that handles the restore operations is not running at any point. Calling it manually requires a whole series of parameters that I have no idea how to enter correctly. I've checked the backup files on another computer and the files are fine.
I've tried uninstalling and reinstalling iTunes 10.5 to no effect.
I'm running iTunes 10.5 on a Windows 7 x64 machine syncing to an iPhone 3GS running a clean iOS5 install.
Does anyone have any ideas on how I can force AppleMobileSync to run or any way to make the restore run through peoperly.

Hi,
Database: Database error 257 at CON
Database: > ORA-00257: archiver error.
Its pointing to Archive Stuck issue. Free some space in the directory of the offline redo logs.
Please move the old or all Archive log files from ORAARCH / SAPARCH directory to other safe location as backup copies and Restart ur DB Instance and SAP Instance step by step.
If this directory is full on the operating system or some problem occurs with it, then the Oracle does not allow overwriting and hence the database is stopped until the archiving process can be restarted successfully.
Sufficient space should be allocated for ORAARCH or SAPARCH directory.
As an alternative, You can disable Archive log mode during SGEN operation. But make sure that you will have to perform immediate offline backup of Database before or after disabling/enabling Archive Log Mode to have guaranteed DB recovery.
Regards,
Bhavik G. Shroff

Archive stuck

Similar Messages

Maybe you are looking for