System Copy(homogenous) Error -Database load phase

Hello All,
I am doing System Copy thorugh Export - Import meothed of SAP R/3 4.7 110 on Windows2003-SQL 2000 SP3. Making Copy of Production server with different SID.After taking Export Successfully from Production Server I am Importing it to Target System
but i am facing error at Database Load Phase getting the same error on almost every process like SAPSSEXE,SAPCLUST,SAPAPPL0,SAPAPPL1 etc. the error is below :
E:\usr\sap\PRT\SYS\exe\run/R3load.exe: START OF LOG: 20090808202046
E:\usr\sap\PRT\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#6 $ SAP
E:\usr\sap\PRT\SYS\exe\run/R3load.exe: version R6.20/V1.2
E:\usr\sap\PRT\SYS\exe\run/R3load.exe -ctf I C:\EXPORT/DATA/SAPAPPL1.STR C:\EXPORT/DB/DDLMSS.TPL C:\SAPinst MSSQL SAPINST3/SAPAPPL1.TSK MSS -l C:\SAPinst MSSQL SAPINST3/SAPAPPL1.log
E:\usr\sap\PRT\SYS\exe\run/R3load.exe: job completed
E:\usr\sap\PRT\SYS\exe\run/R3load.exe: END OF LOG: 20090808202047
E:\usr\sap\PRT\SYS\exe\run/R3load.exe: START OF LOG: 20090808202053
E:\usr\sap\PRT\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#6 $ SAP
E:\usr\sap\PRT\SYS\exe\run/R3load.exe: version R6.20/V1.2
E:\usr\sap\PRT\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\SAPinst MSSQL SAPINST3/SAPAPPL1.cmd -l C:\SAPinst MSSQL SAPINST3/SAPAPPL1.log -loadprocedure fast
DbSl Trace: SQLOLEDB Provider Release:08.10.3959
DbSl Trace: Shared cache sizes: header 52 bytes, 10000 names (13360000 bytes), 1000 dynamic statements (5436000 bytes), total 18796052 bytes
DbSl Trace: Initializing private procedure name cache.
DbSl Trace: procedure cache created/attached
DbSl Trace: Thank You for using the SLOLEDB-interface
DbSl Trace: Connected to db server : [prdt], dbname: PRT, dbuser: prt
DbSl Trace: Using dynamic link library 'E:\usr\sap\PRT\SYS\exe\run\dbmssslib.dll'
DbSl Trace: dbmssslib.dll patch info
DbSl Trace:   patchlevel   0
DbSl Trace:   patchno      524
DbSl Trace:   patchcomment DBDYNPSOURCE/DBDYNPSOURCE~, SHADOW_IMPORT_ALL (578789)
DbSl Trace: The IRow interface is supported by this OLEDB provider
DbSl Trace: ParamStmtExec: line 23573. hr: 0x80040e37 Invalid object name 'SVERS'.
DbSl Trace: HandleOledbError [ParamStmtExec,line 23573]: Error/Message: (err 208, sev 16), Invalid object name 'SVERS'.
DbSl Trace: ParamStmtExec failed.  HR 80040e37 DBSL retcode 103. stmt: [SELECT VERSION AS c FROM SVERS ]
DbSl Trace: Conn_i:1 selection:1 singleton:1 flag_fupd:0 use_cursor:0 chksum:12157
DbSl Trace: DbSlRead - Error 103 (dbcode 208) on open
DbSl Trace: DbSlRead - <##Y2PRDTprt00000035720000000001202054>
DbSl Trace: DbSlRead - Error 103 (dbcode 208) on fetch
DbSl Trace: DbSlRead - <##Y2PRDTprt00000035720000000001202054>
Sat Aug 08 20:20:54 2009
**LOG BZA=> table SVERS      does not exist on database [dblink#1 @ 1292] [dblink  1292 ]
(DB) INFO: connected to DB
(GSI) INFO: dbname   = "PRTprdt                                                                                "
(GSI) INFO: vname    = "MSSQL                           "
(GSI) INFO: hostname = "PRDT                                                            "
(GSI) INFO: sysname  = "Windows NT"
(GSI) INFO: nodename = "PRDT"
(GSI) INFO: release  = "5.2"
(GSI) INFO: version  = "3790 Service Pack 2"
(GSI) INFO: machine  = "2x Intel 80686 (Mod 15 Step 2)"
DbSl Trace: ParamStmtExec: line 23573. hr: 0x80040e37 Invalid object name 'SVERS'.
DbSl Trace: HandleOledbError [ParamStmtExec,line 23573]: Error/Message: (err 208, sev 16), Invalid object name 'SVERS'.
DbSl Trace: ParamStmtExec failed.  HR 80040e37 DBSL retcode 103. stmt: [SELECT VERSION AS c FROM SVERS ]
DbSl Trace: Conn_i:1 selection:1 singleton:1 flag_fupd:0 use_cursor:0 chksum:12157
DbSl Trace: DbSlRead - Error 103 (dbcode 208) on open
DbSl Trace: DbSlRead - <##Y2PRDTprt00000035720000000002202054>
DbSl Trace: DbSlRead - Error 103 (dbcode 208) on fetch
DbSl Trace: DbSlRead - <##Y2PRDTprt00000035720000000002202054>
Interface access functions from dynamic library dbmssslib.dll loaded.(IMP) INFO: import of /1DF/__GI000 completed (0 rows)
(IMP) INFO: import of /BDL/BADHOST completed (0 rows)
(IMP) INFO: import of /BDL/CUSTSES completed (0 rows)
(IMP) INFO: import of /BDL/INTSESS completed (0 rows)
(IMP) INFO: import of /BDL/MSGLOG completed (0 rows)
(IMP) INFO: import of /BDL/NOHOSTS completed (0 rows)
(IMP) INFO: import of /BDL/SESDEST completed (0 rows)
(IMP) INFO: import of /BDL/SESS completed (0 rows)
(IMP) INFO: import of /BDL/STATUS completed (0 rows)
(IMP) INFO: import of /BDL/TESTSES completed (0 rows)
(IMP) INFO: import of /BDL/TRHOSTS completed (0 rows)
(IMP) INFO: import of /SAPDMC/LSOFIL completed (56 rows)
(IMP) INFO: import of /SAPDMC/LSOFIW completed (0 rows)
(IMP) INFO: import of /SAPDMC/LSOPRT completed (0 rows)
(IMP) INFO: import of /SAPSLL/BWHSTR3 completed (0 rows)
(IMP) INFO: import of /SAPSLL/CUWLAR3 completed (0 rows)
(IMP) INFO: import of /SAPSLL/KMATWLR3 completed (0 rows)
(IMP) INFO: import of /SAPSLL/OBJIDX completed (0 rows)
(IMP) INFO: import of /SAPSLL/OBJSSF completed (0 rows)
(IMP) INFO: import of /SAPSLL/OBJSYNC completed (0 rows)
(IMP) INFO: import of /SAPSMOSS/UPDATE completed (0 rows)
(IMP) INFO: import of /SAPTRX/AOTREF completed (0 rows)
(IMP) INFO: import of /SAPTRX/APPTALOG completed (0 rows)
(IMP) INFO: import of /SAPTRX/ASITEMID completed (0 rows)
(IMP) INFO: import of /SAPTRX/MTOBJLOG completed (0 rows)
(IMP) INFO: import of /SCMB/DF_DEL_TAB completed (0 rows)
(IMP) INFO: import of /SCMB/DF_DNET completed (0 rows)
(IMP) INFO: import of /SCMB/DF_DOC completed (0 rows)
(IMP) INFO: InitFastLoad failed with <3: (null)>(IMP) INFO: DBSL will be used(IMP) INFO: import of /SCMB/DF_DOC_VAL
completed (0 rows)
(IMP) INFO: import of /SCMB/DF_DQTY completed (0 rows)
(IMP) INFO: import of /SCMB/DF_DVALUE completed (0 rows)
(IMP) INFO: InitFastLoad failed with <3: (null)>(IMP) INFO: DBSL will be used(IMP) INFO: import of /SCMB/TREEVIEW2 completed
(0 rows)
(IMP) INFO: import of /SDF/INDX completed (0 rows)
(IMP) INFO: import of /SDF/SDBAH completed (0 rows)
(IMP) INFO: import of /SOMO/JOSCHEDL completed (0 rows)
(IMP) INFO: import of /SOMO/JOSCHEDLT completed (0 rows)
(IMP) INFO: import of /SSF/DHEAD completed (1 rows)
(IMP) INFO: InitFastLoad failed with <3: (null)>(IMP) INFO: DBSL will be used(IMP) INFO: import of /SSF/DTAB completed (18
rows)
(IMP) INFO: InitFastLoad failed with <3: (null)>(IMP) INFO: DBSL will be used(IMP) INFO: import of /SSF/PTAB completed (7520 rows)
(IMP) INFO: import of A055 completed (0 rows)
(IMP) INFO: import of A056 completed (0 rows)
(IMP) INFO: import of A064 completed (0 rows)
(IMP) INFO: import of A065 completed (0 rows)
(IMP) INFO: import of ABDBG_BPS completed (0 rows)
(IMP) INFO: import of ABDBG_INFO completed (0 rows)
(IMP) INFO: import of ACCRPOST completed (0 rows)
(IMP) INFO: import of ACCTCR completed (7346418 rows)
(IMP) INFO: import of ACCTHD completed (624272 rows)
(IMP) INFO: import of ACCTIT completed (3673209 rows)
(IMP) INFO: import of ACEPSOH completed (0 rows)
(IMP) INFO: import of ACEPSOI completed (0 rows)
(IMP) INFO: import of ACEPSOIT completed (0 rows)
(IMP) INFO: import of ACL_ACE completed (0 rows)
(IMP) INFO: import of ACL_ACTGR completed (0 rows)
(IMP) INFO: import of ACL_ACTGRE completed (0 rows)
(IMP) INFO: import of ACL_ACTGRT completed (0 rows)
(IMP) INFO: import of ACL_ACTVT completed (0 rows)
(IMP) INFO: import of ACL_ACTVTT completed (0 rows)
(IMP) INFO: import of ACL_CACHE completed (0 rows)
(IMP) INFO: import of ACL_MAIN completed (0 rows)
(IMP) INFO: import of ACL_OBJTP completed (0 rows)
(IMP) INFO: import of ACL_OBJTPA completed (0 rows)
(IMP) INFO: import of ACL_OBJTPG completed (0 rows)
(IMP) INFO: import of ACL_OBJTPT completed (0 rows)
(IMP) INFO: import of ACL_OWNER completed (0 rows)
(IMP) INFO: import of ACRELATION completed (76954 rows)
(IMP) INFO: import of ACTFLI completed (0 rows)
(IMP) INFO: import of AD01DLI completed (0 rows)
(IMP) INFO: import of AD01DLIEF completed (0 rows)
(IMP) INFO: import of AD01DLISF completed (0 rows)
(IMP) INFO: import of AD01FILTVAR completed (0 rows)
(IMP) INFO: import of AD01STRUCTVAR completed (0 rows)
(IMP) INFO: import of AD01VARMASTER completed (0 rows)
(IMP) INFO: import of ADATABSIZE completed (0 rows)
(IMP) INFO: import of ADJT_TRANSACTION completed (0 rows)
(IMP) INFO: import of ADMI_BUFFC completed (0 rows)
(IMP) INFO: import of ADMI_BUFFI completed (0 rows)
(IMP) INFO: import of ADMI_FILES completed (0 rows)
(IMP) INFO: import of ADMI_JOBS completed (0 rows)
(IMP) INFO: import of ADMI_RJOBS completed (0 rows)
(IMP) INFO: import of ADMI_RUN completed (0 rows)
(IMP) INFO: import of ADMI_SKIP completed (0 rows)
(IMP) INFO: import of ADMI_STATS completed (0 rows)
(IMP) INFO: import of ADMI_VARIA completed (0 rows)
(IMP) INFO: import of ADMI_XDOCS completed (0 rows)
(IMP) INFO: import of ADMI_XRUN completed (0 rows)
(IMP) INFO: import of AFAB completed (0 rows)
(IMP) INFO: import of AFBP completed (0 rows)
(IMP) INFO: import of AFFH completed (0 rows)
(IMP) INFO: import of AFFL completed (366118 rows)
(IMP) INFO: import of AFFT completed (0 rows)
(IMP) INFO: import of AFFV completed (0 rows)
(IMP) INFO: import of AFFW completed (7 rows)
(IMP) INFO: import of AFFWPRO completed (0 rows)
(IMP) INFO: import of AFIH completed (113 rows)
The above error are also present in the other Process log files.
But when i saw the installation logs of the Source system the same errors are also there(but it was still Sucessfull Standard installation).
there is one difference as well I am SQL SP3 (8.00.780) but existing Production server is SQL SP3(8.00.929).
My installation is stoppoing here with error While executing Script.
I've done Homogenous copy on WiN-ORACLE many times but on WIN-SQL i am doing very first time.
While installation database phase it asked me for EXPORT CD twice first time for standard(which usually we got with SAP Software) and Second time for Migration EXPORT. that is different from ECC5.0 i think.
Any suggestions?
Regards,
Vinay
Edited by: Vinay Paul on Aug 8, 2009 11:01 PM

Dear Markus,
Thanks for the Reply.
As you Said i am upgrading my kernal (making it same as current kernel using bysource system that is 175).
Hope this will solve my problem ....Do i have to restart my complete installation now?
My recent last error was :
SAPSSRC.LOG
E:\usr\sap\PRT\SYS\exe\run/R3load.exe: START OF LOG: 20090808202048
E:\usr\sap\PRT\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#6 $ SAP
E:\usr\sap\PRT\SYS\exe\run/R3load.exe: version R6.20/V1.2
E:\usr\sap\PRT\SYS\exe\run/R3load.exe -ctf I C:\EXPORT/DATA/SAPSSRC.STR C:\EXPORT/DB/DDLMSS.TPL C:\SAPinst MSSQL SAPINST3/SAPSSRC.TSK MSS -l C:\SAPinst MSSQL SAPINST3/SAPSSRC.log
E:\usr\sap\PRT\SYS\exe\run/R3load.exe: job completed
E:\usr\sap\PRT\SYS\exe\run/R3load.exe: END OF LOG: 20090808202048
E:\usr\sap\PRT\SYS\exe\run/R3load.exe: START OF LOG: 20090808221527
E:\usr\sap\PRT\SYS\exe\run/R3load.exe: sccsid @(#) $Id: //bas/620/src/R3ld/R3load/R3ldmain.c#6 $ SAP
E:\usr\sap\PRT\SYS\exe\run/R3load.exe: version R6.20/V1.2
E:\usr\sap\PRT\SYS\exe\run/R3load.exe -dbcodepage 1100 -i C:\SAPinst MSSQL SAPINST3/SAPSSRC.cmd -l C:\SAPinst MSSQL SAPINST3/SAPSSRC.log -loadprocedure fast
DbSl Trace: SQLOLEDB Provider Release:08.10.3959
DbSl Trace: Shared cache sizes: header 52 bytes, 10000 names (13360000 bytes), 1000 dynamic statements (5436000 bytes), total 18796052 bytes
DbSl Trace: Initializing private procedure name cache.
DbSl Trace: procedure cache created/attached
DbSl Trace: Thank You for using the SLOLEDB-interface
DbSl Trace: Connected to db server : [prdt], dbname: PRT, dbuser: prt
DbSl Trace: Using dynamic link library 'E:\usr\sap\PRT\SYS\exe\run\dbmssslib.dll'
DbSl Trace: dbmssslib.dll patch info
DbSl Trace:   patchlevel   0
DbSl Trace:   patchno      524
DbSl Trace:   patchcomment DBDYNPSOURCE/DBDYNPSOURCE~, SHADOW_IMPORT_ALL (578789)
DbSl Trace: The IRow interface is supported by this OLEDB provider
(DB) INFO: connected to DB
(GSI) INFO: dbname   = "PRTprdt                                                                                "
(GSI) INFO: vname    = "MSSQL                           "
(GSI) INFO: hostname = "PRDT                                                            "
(GSI) INFO: sysname  = "Windows NT"
(GSI) INFO: nodename = "PRDT"
(GSI) INFO: release  = "5.2"
(GSI) INFO: version  = "3790 Service Pack 2"
(GSI) INFO: machine  = "2x Intel 80686 (Mod 15 Step 2)"
Interface access functions from dynamic library dbmssslib.dll loaded.(IMP) INFO: import of ABTREE completed (39 rows)
(IMP) INFO: import of AKB_CHKCONF completed (0 rows)
(IMP) INFO: import of AKB_INDX completed (0 rows)
(IMP) INFO: import of APTREE completed (1531 rows)
(IMP) INFO: import of APTREET completed (75 rows)
(IMP) INFO: import of CAPTREE completed (0 rows)
(IMP) INFO: import of CAPTREET completed (0 rows)
(IMP) INFO: import of CCCEXIT completed (44 rows)
(IMP) INFO: import of CCCINFO completed (15 rows)
(IMP) INFO: import of CLMCUS completed (0 rows)
(IMP) INFO: import of CONTCOMP completed (2 rows)
(IMP) INFO: import of CONTCOMPT completed (4 rows)
(IMP) INFO: import of CONTCOMPX completed (2 rows)
(IMP) INFO: import of CONTCOMPXT completed (3 rows)
(IMP) INFO: import of CROSS completed (1399548 rows)
(IMP) INFO: import of CUSTDIR completed (0 rows)
(IMP) INFO: import of CWBMODILOG completed (0 rows)
(IMP) INFO: import of DBDATA completed (0 rows)
(IMP) INFO: import of DIRTREE completed (21 rows)
(IMP) INFO: import of DVSEQDIR completed (0 rows)
(IMP) INFO: import of DWTREE completed (522 rows)
(IMP) INFO: import of EUDIAL completed (0 rows)
(IMP) INFO: import of EUF4VALUES completed (34 rows)
(IMP) INFO: import of EUFUNC completed (76 rows)
(IMP) INFO: import of EUIMPORT completed (47 rows)
(IMP) INFO: import of EUINFO completed (2772 rows)
(IMP) INFO: import of EUINFOLI completed (0 rows)
(IMP) INFO: import of FUSEQDIR completed (0 rows)
(IMP) INFO: import of GUIDIR completed (0 rows)
(IMP) INFO: import of GUIDIRT completed (3 rows)
(IMP) INFO: import of GUINODE completed (0 rows)
(IMP) INFO: import of GUINODT completed (0 rows)
(IMP) INFO: import of ICON completed (982 rows)
(IMP) INFO: import of ICONP completed (149 rows)
(IMP) INFO: import of ICONT completed (3361 rows)
(IMP) INFO: import of ICO_P completed (0 rows)
(IMP) INFO: import of LDBS completed (0 rows)
(IMP) INFO: import of MAPPARAREF completed (0 rows)
(IMP) INFO: import of MODACT completed (0 rows)
(IMP) INFO: import of MODATTR completed (0 rows)
(IMP) INFO: import of MODIDIR completed (0 rows)
(IMP) INFO: import of MODSAPA completed (2049 rows)
(IMP) INFO: import of MODSAPT completed (3991 rows)
(IMP) INFO: import of MODTEXT completed (0 rows)
(IMP) INFO: import of O2APPL completed (164 rows)
(IMP) INFO: import of O2APPLT completed (305 rows)
(IMP) INFO: import of O2PAGCON completed (4120 rows)
(IMP) INFO: import of O2THEMEREL completed (0 rows)
(IMP) INFO: import of O2THEMES completed (1 rows)
(IMP) INFO: import of O2THEMEST completed (0 rows)
(IMP) INFO: import of O2XMLDESC completed (89 rows)
(IMP) INFO: import of O2XSLTDESC completed (163 rows)
(IMP) INFO: import of O2XSLTOTR completed (0 rows)
(IMP) INFO: import of O2XSLTTEXT completed (385 rows)
(IMP) INFO: import of OBJ_DIFF completed (0 rows)
(IMP) INFO: import of OXT_PICTURE completed (146 rows)
(IMP) INFO: import of PACKCHECK_EXCEPT completed (131 rows)
(IMP) INFO: import of PRICAT_FIELD completed (172 rows)
(IMP) INFO: import of PRICAT_FIELDT completed (343 rows)
(IMP) INFO: import of PROP_ELTYP completed (27 rows)
(IMP) INFO: import of RLB_DB_LB completed (2 rows)
(IMP) INFO: import of RLB_DB_LBT completed (4 rows)
(IMP) INFO: import of RLB_DB_PR completed (31 rows)
(IMP) INFO: import of RLB_DB_PRT completed (62 rows)
(IMP) INFO: import of RLIB_CONT completed (0 rows)
(IMP) INFO: import of RLIB_OBJS completed (1160 rows)
(IMP) INFO: import of RLIB_TREES completed (5 rows)
(IMP) INFO: import of RSEUINC completed (588382 rows)
(IMP) INFO: import of RSEUMOD completed (49 rows)
(IMP) INFO: import of RSEUTAB completed (0 rows)
(IMP) INFO: import of RSMPCHECK completed (31 rows)
(IMP) INFO: import of RSMPCHECKT completed (62 rows)
(IMP) INFO: import of RSMPTEXTSI completed (0 rows)
(IMP) INFO: import of RSNORMTXT completed (246 rows)
(IMP) INFO: import of SDBUSRSET completed (0 rows)
(IMP) INFO: import of SMODILOG completed (125 rows)
(IMP) INFO: import of SMODILOGI completed (0 rows)
(IMP) INFO: import of SMODIPROJ completed (0 rows)
(IMP) INFO: import of SMODISRC completed (492 rows)
(IMP) INFO: import of SMODISRCI completed (0 rows)
(IMP) INFO: import of SMODITRAN completed (0 rows)
(IMP) INFO: import of SMODIUSER completed (0 rows)
(IMP) INFO: InitFastLoad failed with <3: (null)>(IMP) INFO: DBSL will be used(IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
  rc = 22, table "SPROXDAT"
(IMP) INFO: InitFastLoad failed with <3: (null)>(IMP) INFO: DBSL will be usedDbSl Trace: invalid sign in BCD number: 1
DbSl Trace: Error converting decimal:  000000000200303.0 HEX: 0000000002003031 input variable# 12, proc: ## No proc
DbSl Trace: invalid sign in BCD number: 1
DbSl Trace: Error converting decimal:  000000000200303.0 HEX: 0000000002003031 input variable# 14, proc: ## No proc
DbSl Trace: internal error in decimal conversion.
(IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
  rc = 8, table "SPROXHDR"
(IMP) INFO: import of SPROXINDX completed (0 rows)
(IMP) INFO: import of SPROXKEY completed (0 rows)
(IMP) INFO: import of SPROXREG completed (9 rows)
(IMP) INFO: import of SPROXSET completed (0 rows)
(IMP) INFO: InitFastLoad failed with <3: (null)>(IMP) INFO: DBSL will be used(IMP) INFO: import of SPROXTST completed (0 rows)
(IMP) INFO: import of SRESETLOG completed (0 rows)
(IMP) INFO: import of SRESETLOG2 completed (0 rows)
(IMP) INFO: import of SXC_ATTR completed (1045 rows)
(IMP) INFO: import of SXC_ATTRT completed (1855 rows)
(IMP) INFO: import of SXC_CLASS completed (1045 rows)
(IMP) INFO: import of SXC_COCO completed (0 rows)
(IMP) INFO: import of SXC_EXIT completed (1449 rows)
(IMP) INFO: import of SXC_FCODE completed (11 rows)
(IMP) INFO: import of SXC_FCODET completed (23 rows)
(IMP) INFO: import of SXC_IMPSWH completed (2551 rows)
(IMP) INFO: import of SXC_SCRN completed (47 rows)
(IMP) INFO: import of SXC_TABLE completed (0 rows)
(IMP) INFO: import of SXC_TABLET completed (0 rows)
(IMP) INFO: import of SXS_ATTR completed (2093 rows)
(IMP) INFO: import of SXS_ATTRT completed (4020 rows)
(IMP) INFO: import of SXS_COCO completed (0 rows)
(IMP) INFO: import of SXS_FCODE completed (64 rows)
(IMP) INFO: import of SXS_FCODET completed (128 rows)
(IMP) INFO: import of SXS_INTER completed (2093 rows)
(IMP) INFO: import of SXS_MLCO completed (616 rows)
(IMP) INFO: import of SXS_SCRN completed (80 rows)
(IMP) INFO: import of SXS_SCRNT completed (141 rows)
(IMP) INFO: import of SXS_TABLE completed (1 rows)
(IMP) INFO: import of SXS_TABLET completed (2 rows)
(IMP) INFO: import of SYS_COMP completed (0 rows)
(IMP) INFO: import of TBPROGREF completed (251 rows)
(IMP) INFO: import of TBVIEWER completed (0 rows)
(IMP) INFO: import of TCG01 completed (9 rows)
(IMP) INFO: import of TCP11 completed (1 rows)
(IMP) INFO: import of TCP13 completed (0 rows)
(IMP) INFO: import of TCP17 completed (0 rows)
(IMP) INFO: import of TGLIF completed (534 rows)
(IMP) INFO: import of THELPI completed (0 rows)
(IMP) INFO: import of TMCRT completed (303 rows)
(IMP) INFO: import of TMEMO completed (0 rows)
(IMP) INFO: import of TRANSFDESC completed (0 rows)
(IMP) INFO: import of TRANSFTEXT completed (0 rows)
(IMP) INFO: import of TRDIRE completed (32350 rows)
(IMP) INFO: import of TREELOG completed (15990 rows)
(IMP) INFO: import of W3HTMLT completed (1138 rows)
(IMP) INFO: import of W3HTRCT completed (162 rows)
(IMP) INFO: import of W3JSCRT completed (0 rows)
(IMP) INFO: import of W3MIMET completed (361 rows)
(IMP) INFO: import of W3OBJLOINF completed (0 rows)
(IMP) INFO: import of W3PUBDIR completed (0 rows)
(IMP) INFO: import of W3SERINTP completed (44 rows)
(IMP) INFO: import of W3SERINTPT completed (63 rows)
(IMP) INFO: import of W3SERVICET completed (156 rows)
(IMP) INFO: import of WBCROSSGT completed (126383 rows)
(IMP) INFO: import of WBCROSSI completed (5654 rows)
(DB) INFO: disconnected from DB
E:\usr\sap\PRT\SYS\exe\run/R3load.exe: job finished with 2 error(s)
E:\usr\sap\PRT\SYS\exe\run/R3load.exe: END OF LOG: 20090808221726
Regards,
Vinay

Similar Messages

  • The Java load in database SID / hostname has not been configured yet. You cannot run an installation from the System Copy folder with this load

    Dear Gurus,
    We are facing the below issue when performing a homogeneous system copy of NW 7.0 system using backup/restore method for DB6 system.
    The Java load in database <SID>/<hostname> has not been configured yet. You cannot run an installation from the System Copy folder with this load.
    We went through the SAP Note http://service.sap.com/sap/support/notes/2049842, and followed the same but no luck.
    We updated the Kernel to the latest, but still no luck.
    Request for your quick help as we have to complete it by EOD today.
    Thanks a lot in advance.
    Best Regards,
    Anuj

    Hello Ashutosh ,
    Thanks for your reply.
    We have gone followed the below sequence:
    SCS Installation
    Database Instance Installation using backup/restore method
    CI installation. -> getting error, when we provide the Java Components DVD.
    Best Regards,
    Anuj

  • System Copy Homogeneous

    Dear Gurus!
    I'm executing a "System Copy Homogeneous" with the CD51020587 in i570 server V5R3M0 operation system.
    But the instance profile can't created and when I've created manually, this shows message:
    "El desplazamiento de espacio X'00000000' o X'000000022E002040' está fuera
    del límite actual para el objeto QPADEV0002QSECOFR 003702.
    Error de aplicación. MCH0601 no supervisado por QC2POSIX en la sentencia
    0000000011, instrucción X'0000'.                  
    Thank you for your help
    Best Regards

    Hi Luis,
    I don't know, if it is really not possible to use this CD (it is not v5r3 certified), but at least you could use the "manual approach" of the system copy as described e.g. in:
    http://tech.groups.yahoo.com/group/SAPoniSeries/files/
    Database Copy as of 46B.htm
    or
    Delete&Rebuild_TST_SID_from P01.doc
    Regards
    Volker Gueldenpfennig, consolut.gmbh
    http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

  • Why NetWeaver04 DB instance takes more time during 'Database Load' phase?

    Hi,
    I'm installing NetWeaver04 CI and DB instances on Solaris 10 machine and as a standalone installation. CI was installed fine and DB instance install takes forever and i don't know how long it will take because i started this at 17.20 and now it is 22.01. Here is the summary of my install.
    1. Installed CI
    Note: Unicode ABAP install
    2. Ran DB instance install:
    Note:Selected Advanced database options instead of RAW device
    3. Completed Oracle install and continued for DB instance install
    Note: Selected Unicode option and selected Enterprise install
    4. The install so far completed 25 out of 39 tasks and it is waiting for more than 4 hrs at Database Load phase.
    I'm not sure what will be the result of my install. I would like to know whether it is supposed to take that long for DB instance install. Could someone tell me what would be the reason and what would i've missed in the install steps.
    Thanks,
    Ram

    The load is by far the most time consuming operation; you can make this run faster if you have a large amount of hardware by increasing the number of parallel R3trans jobs (default is 3) during the installation.  It's not uncommon for this step to run for several hours if you don't increase this parameter.
    Also, you might watch the oracle alert log; if your archive directory fills up, the load will just hang indefinitly.  If you create your oraarch filesystem with at least 4 GB of space, this shouldn't be an issue during the initial load, but if it's much smaller, you could run into a problem there....
    Rich

  • System Copy Homogeneous SAP R/3 5.0

    Hi gurus..
    I need the manual System copy homogeneous for windows 2003 and SQL 2005
    in SAP R/3 5.0
    Thank you for your help
    Luis

    Hi Gurus!!
    I've installed an system SAP 5.0,  SID= DET,  SN= 01,  HOST=SRV01037. in Windows 2003 and SQL 2005 in HP server, this has been finnished succesfull.
    Now I've executed backup of the data base of another server HOST=SRV01053, SID=DEV, SN=00 and this data base has been restored in the SRV01037 server, but when I start the instance, the disp+work stopped.
    I need know what's the correct procedure, to executed this operation.
    Best Regards.
    Luis Salazar

  • Assertion failed: Unable to load database SID during sybase system copy on Linux in the phase "Create DB"

    Hi Supports,
    I am using sapinst homogeneous system copy in Linux on sybase.
    I stuck on the the step 27/49 "create Database".
    I checked Firewall is off.
    i got  points in my sapinst_dev.log that "
    1)The log segment in the target database 'SID' is too small (9216 MB) to accommodate the log segment from the dumped database (10240 MB)"
    and
    2)"Can't change the owner of the master, model, tempdb or sybsystemprocs database"
    Do i need to increase "sybase/SID/saplog_1" ?  because my "saplog_1" is 49 mb now.
    if it is ! how do i increase in this stage.
    can any one know about this error???
    Thanks,
    Aziz.

    Hi,
    When i seen SID.log file so its showing deadlock and checkpoint occurring,
    Is any solution ???
    Is this because of networks?
    we had 2 servers on this same IP. but i stopped one server and one is still running.
    please find my SID.log file and revert back if any soltion.
    ==========================================================
    =~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2014.03.21 12:12:31 =~=~=~=~=~=~=~=~=~=~=~=
    ibssrv02:/sybase/IB1/ASE-15_0/install #
    ibssrv02:/sybase/IB1/ASE-15_0/install # lscd ASE-15_0/install/lscd IB1lscd /IB1sybase/df -hexitsu - sybib1lscd IB1ls
    IB1.log  IB1_BS.log  IB1_JSAGENT.log  RUN_IB1  RUN_IB1_BS  auditinit  setperm_all  showserver  startserver  sybhauser  veritas
    ibssrv02:/sybase/IB1/ASE-15_0/install # more IB1.log
    00:0000:00000:00000:2014/03/21 11:03:36.98 kernel  SySAM: Using licenses from: /sybase/IB1/SYSAM-2_0/licenses/SYBASE.lic:/sybase/IB1/SYSAM-2_0/licenses/SYBASE_ASE_DE.li
    c:/sybase/IB1/SYSAM-2_0/licenses/SYBASE_ASE_XE.lic
    00:0000:00000:00000:2014/03/21 11:03:37.00 kernel  SySAM: Checked out license for 6 ASE_CORE (2014.1231/permanent/1296 8FE3 0A83 A167).
    00:0000:00000:00000:2014/03/21 11:03:37.00 kernel  This product is licensed to: SAP, for use with SAP Business Applications.
    00:0000:00000:00000:2014/03/21 11:03:37.00 kernel  Checked out license ASE_CORE
    00:0000:00000:00000:2014/03/21 11:03:37.00 kernel  Adaptive Server Enterprise (Enterprise Edition)
    00:0000:00000:00000:2014/03/21 11:03:37.00 kernel  Performing space allocation for device '/sybase/IB1/sybsystem/master.dat' (0.39 Gb).  This may take some time.
    00:0000:00000:00000:2014/03/21 11:03:38.32 kernel  Finished initialization.
    00:0000:00000:00000:2014/03/21 11:03:38.32 kernel  Using config area from primary master device.
    00:0000:00000:00000:2014/03/21 11:03:38.32 server  Configuration Error: Configuration file, '/sybase/IB1/IB1.cfg', does not exist.
    00:0000:00000:00000:2014/03/21 11:03:38.32 kernel  Warning: A configuration file was not specified or the default file '/sybase/IB1/IB1.cfg' does not exist. ASE creates
    the default file.
    00:0000:00000:00000:2014/03/21 11:03:38.32 kernel  Warning: Using default file '/sybase/IB1/IB1.cfg' since a configuration file was not specified. Specify a configurati
    on file name in the RUNSERVER file to avoid this message.
    00:0000:00000:00000:2014/03/21 11:03:38.33 kernel  Could not allocate memory using Huge Pages. Allocated using regular pages. For better performance, reboot the server
    after configuring enough Huge Pages.
    00:0000:00000:00000:2014/03/21 11:03:38.33 kernel  Internal run-time model set for Linux  - Native
    00:0000:00000:00000:2014/03/21 11:03:38.33 kernel  Adaptive Server is using the threaded kernel mode.
    00:0000:00000:00000:2014/03/21 11:03:38.33 kernel  Using 4096 file descriptors.
    00:0000:00000:00000:2014/03/21 11:03:38.33 kernel  Adaptive Server Enterprise/15.7/EBF 21341 SMP SP101 /P/x86_64/Enterprise Linux/ase157sp101/3439/64-bit/FBO/Thu Jun  6
    16:08:18 2013
    00:0000:00000:00000:2014/03/21 11:03:38.33 kernel  Confidential property of Sybase, Inc.
    00:0000:00000:00000:2014/03/21 11:03:38.33 kernel  Copyright 1987, 2013
    00:0000:00000:00000:2014/03/21 11:03:38.33 kernel  Sybase, Inc.  All rights reserved.
    00:0000:00000:00000:2014/03/21 11:03:38.33 kernel  Unpublished rights reserved under U.S. c 1702]: noting the present database upgrade level
    00:0006:00000:00001:2014/03/21 11:03:39.77 server  Database 'master': beginning upgrade step [ID  1718]: executing SQL statement ("update master.dbo.sysusages set loc..
    00:0006:00000:00001:2014/03/21 11:03:39.77 server  Database 'master': beginning upgrade step [ID  1719]: executing SQL statement ("update sysattributes set object_inf..
    00:0006:00000:00001:2014/03/21 11:03:39.77 server  Database 'master': beginning upgrade step [ID  1720]: noting the present database upgrade level
    00:0006:00000:00001:2014/03/21 11:03:39.77 server  Database 'master': beginning upgrade step [ID  1730]: noting the present database upgrade level
    00:0006:00000:00001:2014/03/21 11:03:39.77 server  Database 'master': beginning upgrade step [ID  1731]: executing SQL statement ("begin declare @val int select @val=..
    00:0006:00000:00001:2014/03/21 11:03:39.77 server  Database 'master': beginning upgrade step [ID  1740]: noting the present database upgrade level
    00:0006:00000:00001:2014/03/21 11:03:39.77 server  Database 'model' does not exist. ASE will create it.
    --More--(11%)
    00:0006:00000:00001:2014/03/21 11:03:39.77 server  Database 'model': beginning upgrade step [ID     1]: Initialize disk and create empty allocation units on master devi
    ce.
    00:0006:00000:00001:2014/03/21 11:03:39.79 server  Database 'model': beginning upgrade step [ID     2]: Bootstrap basic system catalogs in database.
    00:0006:00000:00001:2014/03/21 11:03:39.79 server  Database 'model': beginning upgrade step [ID     6]: creating index (table syspartitions, index ncsyspartitions)
    00:0006:00000:00001:2014/03/21 11:03:39.80 server  Database 'model': beginning upgrade step [ID     8]: creating index (table systypes, index ncsystypes)
    00:0006:00000:00001:2014/03/21 11:03:39.80 server  Database 'model': beginning upgrade step [ID    10]: creating index (table sysobjects, index ncsysobjects)
    00:0006:00000:00001:2014/03/21 11:03:39.80 server  Database 'model': beginning upgrade step [ID    13]: creating table (table systabstats)
    00:0006:00000:00001:2014/03/21 11:03:39.80 server  Database 'model': beginning upgrade step [ID    26]: creating table (table sysprocedures)
    00:0006:00000:00001:2014/03/21 11:03:39.80 server  Database 'model': beginning upgrade step [ID    27]: creating table (table syscomments)
    00:0006:00000:00001:2014/03/21 11:03:39.80 server  Database 'model': beginning upgrade step [ID    28]: creating table (table syssegments)
    00:0006:00000:00001:2014/03/21 11:03:39.81 server  Database 'model': beginning upgrade step [ID    29]: creating table (table sysprotects)
    00:0006:00000:00001:2014/03/21 11:03:39.81 server  Database 'model': beginning upgrade step [ID    30]: creating table (table sysusers)
    00:0006:00000:00001:2014/03/21 11:03:39.81 server  Database 'model': beginning upgrade step [ID    31]: creating table (table sysalternates)
    00:0006:00000:00001:2014/03/21 11:03:39.81 server  Database 'model': beginning upgrade step [ID    32]: creating table (table sysdepends)
    00:0006:00000:00001:2014/03/21 11:03:39.81 server  Database 'model': beginning upgrade step [ID    33]: creating table (table syskeys)
    00:0006:00000:00001:2014/03/21 11:03:39.82 server  Database 'model': beginning upgrade step [ID    47]: creating table (table syspartitionkeys)
    00:0006:00000:00001:2014/03/21 11:03:39.82 server  Database 'model': beginning upgrade step [ID    51]: creating table (table sysreferences)
    00:0006:00000:00001:2014/03/21 11:03:39.82 server  Database 'model': beginning upgrade step [ID    52]: creating table (table sysconstraints)
    00:0006:00000:00001:2014/03/21 11:03:39.83 server  Database 'model': beginning upgrade step [ID    53]: creating table (table sysusermessages)
    00:0006:00000:00001:2014/03/21 11:03:39.83 server  Database 'model': beginning upgrade step [ID    54]: creating table (table systhresholds)
    00:0006:00000:00001:2014/03/21 11:03:39.83 server  Database 'model': beginning upgrade step [ID    55]: creating table (table sysroles)
    00:0006:00000:00001:2014/03/21 11:03:39.83 server  Database 'model': beginning upgrade step [ID    56]: creating table (table sysslices)
    00:0006:00000:00001:2014/03/21 11:03:39.83 server  Database 'model': beginning upgrade step [ID    60]: creating table (table sysstatistics)
    00:0006:00000:00001:2014/03/21 11:03:39.84 server  Database 'model': beginning upgrade step [ID    61]: creating table (table sysxtypes)
    00:0006:00000:00001:2014/03/21 11:03:39.84 server  Database 'model': beginning upgrade step [ID    62]: creating table (table sysjars)
    00:0006:00000:00001:2014/03/21 11:03:39.84 server  Database 'model': beginning upgrade step [ID    65]: creating table (table sysqueryplans)
    00:0006:00000:00001:2014/03/21 11:03:39.85 server  Database 'model': beginning upgrade step [ID    68]: creating table (table sysencryptkeys)
    00:0006:00000:00001:2014/03/21 11:03:39.85 server  Database 'model': beginning upgrade step [ID    73]: executing SQL statement ("update sysobjects set sysstat = sys...
    00:0006:00000:00001:2014/03/21 11:03:39.85 server  Database 'model': beginning upgrade step [ID    74]: executing SQL statement ("update syscolumns set type=66, user...
    00:0006:00000:00001:2014/03/21 11:03:39.85 server  Database 'model': beginning upgrade step [ID    80]: creating table (table sysattributes)
    00:0006:00000:00001:2014/03/21 11:03:39.86 server  Database 'model': beginning upgrade step [ID    82]: creating table (table sysdams)
    00:0006:00000:00001:2014/03/21 11:03:39.86 server  Database 'model': beginning upgrade step [ID    90]: insert basic data into bootstrap system tables
    00:0006:00000:00001:2014/03/21 11:03:39.89 server  Database 'model': beginning upgrade step [ID    91]: executing SQL statement ("update systypes set length=@@maxpag...
    00:0006:00000:00001:2014/03/21 11:03:39.89 server  Database 'model': beginning upgrade step [ID   245]: Update system roles in system tables.
    00:0006:00000:00001:2014/03/21 11:03:39.89 server  Database 'model': beginning upgrade step [ID   248]: update system catalog protection data
    00:0006:00000:00001:2014/03/21 11:03:39.90 server  Database 'model': beginning upgrade step [ID   606]: executing SQL statement ("select lct_admin('lastchance', db_i...
    00:0006:00000:00001:2014/03/21 11:03:39.90 server  Database 'model': beginning upgrade step [ID  1126]: Initialize systabstats with valid statistics
    00:0006:00000:00001:2014/03/21 11:03:39.90 server  Database 'model': beginning upgrade step [ID  1131]: Creating/Updating the last chance threshold for logsegment.
    00:0006:00000:00001:2014/03/21 11:03:39.90 server  Database 'model': beginning upgrade step [ID  1274]: executing SQL statement ("declare @dummy int")
    --More--(13%)
    00:0006:00000:00001:2014/03/21 11:03:39.91 server  Database 'model': beginning upgrade step [ID  1241]: executing SQL statement ("insert into sysattributes (class, a...
    00:0006:00000:00001:2014/03/21 11:03:39.91 server  Database 'model': beginning upgrade step [ID  1400]: noting the present database upgrade level
    00:0006:00000:00001:2014/03/21 11:03:39.91 server  Database 'model': beginning upgrade step [ID  1411]: executing SQL statement ("if not exists (select 1 from master...
    00:0006:00000:00001:2014/03/21 11:03:39.91 server  Database 'model': beginning upgrade step [ID  1416]: executing SQL statement ("update sysroles set id=11 from sysu...
    00:0006:00000:00001:2014/03/21 11:03:39.91 server  Database 'model': beginning upgrade step [ID  1502]: executing SQL statement ("if exists (select 1 from sysobjects...
    00:0006:00000:00001:2014/03/21 11:03:39.91 server  Database 'model': beginning upgrade step [ID  1503]: executing SQL statement ("create view sysquerymetrics (uid, g...
    00:0006:00000:00001:2014/03/21 11:03:39.92 server  Database 'model': beginning upgrade step [ID  1505]: executing SQL statement ("update sysattributes set char_value...
    00:0006:00000:00001:2014/03/21 11:03:39.92 server  Database 'model': beginning upgrade step [ID  1550]: noting the present database upgrade level
    00:0006:00000:00001:2014/03/21 11:03:39.92 server  Database 'model': beginning upgrade step [ID  1554]: upgrade simulated statistics
    00:0006:00000:00001:2014/03/21 11:03:39.92 server  Database 'model': beginning upgrade step [ID  1564]: executing SQL statement ("declare @dbid int select @dbid = db...
    00:0006:00000:00001:2014/03/21 11:03:39.93 server  Database 'model': beginning upgrade step [ID  1650]: executing SQL statement ("dbcc upgd_grantrev_sysrole_perms('g...
    00:0006:00000:00001:2014/03/21 11:03:39.97 server  Database 'model': beginning upgrade step [ID  1651]: updating builtin permissions
    00:0006:00000:00001:2014/03/21 11:03:39.97 server  Database 'model': beginning upgrade step [ID  1652]: adding generic user 'usedb_user' to sysusers
    00:0006:00000:00001:2014/03/21 11:03:39.97 server  Database 'model': beginning upgrade step [ID  1653]: updating DBCC command permissions
    00:0006:00000:00001:2014/03/21 11:03:39.97 server  Database 'model': beginning upgrade step [ID  1702]: noting the present database upgrade level
    00:0006:00000:00001:2014/03/21 11:03:39.97 server  Database 'model': beginning upgrade step [ID  1719]: executing SQL statement ("update sysattributes set object_inf...
    00:0006:00000:00001:2014/03/21 11:03:39.97 server  Database 'model': beginning upgrade step [ID  1720]: noting the present database upgrade level
    00:0006:00000:00001:2014/03/21 11:03:39.97 server  Database 'model': beginning upgrade step [ID  1730]: noting the present database upgrade level
    00:0006:00000:00001:2014/03/21 11:03:39.97 server  Database 'model': beginning upgrade step [ID  1740]: noting the present database upgrade level
    00:0006:00000:00001:2014/03/21 11:03:39.97 server  CREATE DATABASE: allocating 1536 logical pages (24.0 megabytes) on disk 'master' (1536 logical pages requested).
    00:0006:00000:00001:2014/03/21 11:03:39.97 server  Warning: The database 'sybsystemdb' is using an unsafe virtual device 'master'. The recovery of this database can not
    be guaranteed.
    00:0006:00000:00001:2014/03/21 11:03:39.99 server  Timestamp for database 'sybsystemdb' is (0x0000, 0x000013b4).
    00:0006:00000:00001:2014/03/21 11:03:39.99 server  Database 'sybsystemdb' is now online.
    00:0006:00000:00001:2014/03/21 11:03:39.99 server  Database sybsystemdb successfully created.
    00:0006:00000:00001:2014/03/21 11:03:39.99 server  Recovering database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:39.99 server  Started estimating recovery log boundaries for database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:39.99 server  Database 'sybsystemdb', checkpoint=(864, 64), first=(864, 64), last=(864, 150).
    00:0006:00000:00001:2014/03/21 11:03:39.99 server  Completed estimating recovery log boundaries for database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:39.99 server  Started ANALYSIS pass for database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:39.99 server  Completed ANALYSIS pass for database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:39.99 server  Log contains all committed transactions until 2014/03/21 11:03:39.33 for database sybsystemdb.
    00:0006:00000:00001:2014/03/21 11:03:39.99 server  Started REDO pass for database 'sybsystemdb'. The total number of log records to process is 86.
    00:0006:00000:00001:2014/03/21 11:03:39.99 server  Redo pass of recovery has processed 2 committed and 0 aborted transactions.
    --More--(15%)
    00:0006:00000:00001:2014/03/21 11:03:39.99 server  Completed REDO pass for database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:39.99 server  Timestamp for database 'sybsystemdb' is (0x0000, 0x00001416).
    00:0006:00000:00001:2014/03/21 11:03:39.99 server  Recovery of database 'sybsystemdb' will undo incomplete nested top actions.
    00:0006:00000:00001:2014/03/21 11:03:39.99 server  Started recovery checkpoint for database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:39.99 server  Completed recovery checkpoint for database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:39.99 server  Started filling free space info for database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:39.99 server  Completed filling free space info for database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Started cleaning up the default data cache for database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Completed cleaning up the default data cache for database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Boot Count: 1
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking external objects.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Database 'sybsystemdb' is now online.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Now loading ASE's new default sort order and character set
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysobjects' (object ID 1): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysobjects_1' (partition ID 1) of table 'sysobjects'. The logical page size of this table is 1638
    4 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'systypes' (object ID 4): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'systypes_4' (partition ID 4) of table 'systypes'. The logical page size of this table is 16384 by
    tes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysusers' (object ID 10): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysusers_10' (partition ID 10) of table 'sysusers'. The logical page size of this table is 16384
    bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysreferences' (object ID 16): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysreferences_16' (partition ID 16) of table 'sysreferences'. The logical page size of this table
    is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysreferences' (object ID 16): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysreferences_16' (partition ID 16) of table 'sysreferences'. The logical page size of this table
    is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysreferences' (object ID 16): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysreferences_16' (partition ID 16) of table 'sysreferences'. The logical page size of this table
    is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    --More--(17%)
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysattributes' (object ID 21): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysattributes_21' (partition ID 21) of table 'sysattributes'. The logical page size of this table
    is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysattributes' (object ID 21): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysattributes_21' (partition ID 21) of table 'sysattributes'. The logical page size of this table
    is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysxtypes' (object ID 25): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysxtypes_25' (partition ID 25) of table 'sysxtypes'. The logical page size of this table is 1638
    4 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysjars' (object ID 26): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysjars_26' (partition ID 26) of table 'sysjars'. The logical page size of this table is 16384 by
    tes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'syspartitions' (object ID 28): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'syspartitions_28' (partition ID 28) of table 'syspartitions'. The logical page size of this table
    is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysobjects' (object ID 1): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysobjects_1' (partition ID 1) of table 'sysobjects'. The logical page size of this table is 1638
    4 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'systypes' (object ID 4): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'systypes_4' (partition ID 4) of table 'systypes'. The logical page size of this table is 16384 by
    tes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysusers' (object ID 10): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysusers_10' (partition ID 10) of table 'sysusers'. The logical page size of this table is 16384
    bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysreferences' (object ID 16): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysreferences_16' (partition ID 16) of table 'sysreferences'. The logical page size of this table
    --More--(18%)
    is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysreferences' (object ID 16): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysreferences_16' (partition ID 16) of table 'sysreferences'. The logical page size of this table
    is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysreferences' (object ID 16): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysreferences_16' (partition ID 16) of table 'sysreferences'. The logical page size of this table
    is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysattributes' (object ID 21): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysattributes_21' (partition ID 21) of table 'sysattributes'. The logical page size of this table
    is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysattributes' (object ID 21): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysattributes_21' (partition ID 21) of table 'sysattributes'. The logical page size of this table
    is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysxtypes' (object ID 25): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysxtypes_25' (partition ID 25) of table 'sysxtypes'. The logical page size of this table is 1638
    4 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysjars' (object ID 26): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysjars_26' (partition ID 26) of table 'sysjars'. The logical page size of this table is 16384 by
    tes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'syspartitions' (object ID 28): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'syspartitions_28' (partition ID 28) of table 'syspartitions'. The logical page size of this table
    is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysobjects' (object ID 1): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysobjects_1' (partition ID 1) of table 'sysobjects'. The logical page size of this table is 1638
    4 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'systypes' (object ID 4): Logical page size is 16384 bytes.
    --More--(20%)
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'systypes_4' (partition ID 4) of table 'systypes'. The logical page size of this table is 16384 by
    tes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysusers' (object ID 10): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysusers_10' (partition ID 10) of table 'sysusers'. The logical page size of this table is 16384
    bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysreferences' (object ID 16): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysreferences_16' (partition ID 16) of table 'sysreferences'. The logical page size of this table
    is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysreferences' (object ID 16): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysreferences_16' (partition ID 16) of table 'sysreferences'. The logical page size of this table
    is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysreferences' (object ID 16): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysreferences_16' (partition ID 16) of table 'sysreferences'. The logical page size of this table
    is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysattributes' (object ID 21): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysattributes_21' (partition ID 21) of table 'sysattributes'. The logical page size of this table
    is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysattributes' (object ID 21): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysattributes_21' (partition ID 21) of table 'sysattributes'. The logical page size of this table
    is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysxtypes' (object ID 25): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysxtypes_25' (partition ID 25) of table 'sysxtypes'. The logical page size of this table is 1638
    4 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysjars' (object ID 26): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysjars_26' (partition ID 26) of table 'sysjars'. The logical page size of this table is 16384 by
    tes.
    --More--(21%)
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'syspartitions' (object ID 28): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'syspartitions_28' (partition ID 28) of table 'syspartitions'. The logical page size of this table
    is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysdatabases' (object ID 30): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysdatabases_30' (partition ID 30) of table 'sysdatabases'. The logical page size of this table i
    s 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'syslogins' (object ID 33): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'syslogins_33' (partition ID 33) of table 'syslogins'. The logical page size of this table is 1638
    4 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysdevices' (object ID 35): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysdevices_35' (partition ID 35) of table 'sysdevices'. The logical page size of this table is 16
    384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysconfigures' (object ID 37): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking partition 'sysconfigures_37' (partition ID 37) of table 'sysconfigures'. The logical page size of this table
    is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  
    00:0006:00000:00001:2014/03/21 11:03:40.00 server  Checking table 'sysservers' (object ID 40): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  Checking partition 'sysservers_40' (partition ID 40) of table 'sysservers'. The logical page size of this table is 16
    384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  Checking table 'sysremotelogins' (object ID 41): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  Checking partition 'sysremotelogins_41' (partition ID 41) of table 'sysremotelogins'. The logical page size of this t
    able is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  Checking table 'syslanguages' (object ID 44): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  Checking partition 'syslanguages_44' (partition ID 44) of table 'syslanguages'. The logical page size of this table i
    s 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  Checking table 'syslanguages' (object ID 44): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  
    --More--(23%)
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  Checking partition 'syslanguages_44' (partition ID 44) of table 'syslanguages'. The logical page size of this table i
    s 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  Checking table 'syscharsets' (object ID 45): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  Checking partition 'syscharsets_45' (partition ID 45) of table 'syscharsets'. The logical page size of this table is
    16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  Checking table 'sysresourcelimits' (object ID 52): Logical page size is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  Checking partition 'sysresourcelimits_52' (partition ID 52) of table 'sysresourcelimits'. The logical page size of th
    is table is 16384 bytes.
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  Default Sort Order successfully changed.
    00:0006:00000:00001:2014/03/21 11:03:40.01 server  ASE shutdown after verifying System Indexes.
    00:0006:00000:00001:2014/03/21 11:03:40.01 kernel  ueshutdown: exiting
    00:0000:00000:00000:2014/03/21 11:03:40.01 kernel  Main thread performing final shutdown.
    00:0000:00000:00000:2014/03/21 11:03:40.06 kernel  Blocking call queue shutdown.
    00:0000:00000:00000:2014/03/21 11:03:40.21 kernel  SySAM: Checked in license for 6 ASE_CORE (2014.1231/permanent/1296 8FE3 0A83 A167).
    00:0000:00000:00000:2014/03/21 11:03:40.98 kernel  SySAM: Using licenses from: /sybase/IB1/SYSAM-2_0/licenses/SYBASE.lic:/sybase/IB1/SYSAM-2_0/licenses/SYBASE_ASE_DE.li
    c:/sybase/IB1/SYSAM-2_0/licenses/SYBASE_ASE_XE.lic
    00:0000:00000:00000:2014/03/21 11:03:41.00 kernel  SySAM: Checked out license for 6 ASE_CORE (2014.1231/permanent/1296 8FE3 0A83 A167).
    00:0000:00000:00000:2014/03/21 11:03:41.00 kernel  This product is licensed to: SAP, for use with SAP Business Applications.
    00:0000:00000:00000:2014/03/21 11:03:41.00 kernel  Checked out license ASE_CORE
    00:0000:00000:00000:2014/03/21 11:03:41.00 kernel  Adaptive Server Enterprise (Enterprise Edition)
    00:0000:00000:00000:2014/03/21 11:03:41.00 kernel  Using config area from primary master device.
    00:0000:00000:00000:2014/03/21 11:03:41.00 kernel  Could not allocate memory using Huge Pages. Allocated using regular pages. For better performance, reboot the server
    after configuring enough Huge Pages.
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  Internal run-time model set for Linux  - Native
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  Adaptive Server is using the threaded kernel mode.
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  Using 4096 file descriptors.
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  Adaptive Server Enterprise/15.7/EBF 21341 SMP SP101 /P/x86_64/Enterprise Linux/ase157sp101/3439/64-bit/FBO/Thu Jun  6
    16:08:18 2013
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  Confidential property of Sybase, Inc.
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  Copyright 1987, 2013
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  Sybase, Inc.  All rights reserved.
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  Unpublished rights reserved under U.S. copyright laws.
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel 
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  This software contains confidential and trade secret information of Sybase,
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  Inc.   Use,  duplication or disclosure of the software and documentation by
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  the  U.S.  Government  is  subject  to  restrictions set forth in a license
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  agreement  between  the  Government  and  Sybase,  Inc.  or  other  written
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  agreement  specifying  the  Government's rights to use the software and any
    --More--(24%)
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  applicable FAR provisions, for example, FAR 52.227-19.
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  Sybase, Inc. One Sybase Drive, Dublin, CA 94568, USA
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  Using /sybase/IB1 as the 'SYBASE' environment variable, found during startup.
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  Using OCS-15_0 as the 'SYBASE_OCS' environment variable, found during startup.
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  Using ASE-15_0 as the 'SYBASE_ASE' environment variable, found during startup.
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  ASE booted on host 'ibssrv02' running Linux release 3.0.13-0.27-default version #1 SMP Wed Feb 15 13:33:49 UTC 2012 (
    d73692b).
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  Using '/sybase/IB1/ASE-15_0/IB1.cfg' for configuration information.
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  Logging ASE messages in file '/sybase/IB1/ASE-15_0/install/IB1.log'.
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  Disk Controller Manager is online.
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  Network Controller Manager is online.
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  Ct-Lib Controller Manager is online.
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  Platform TCP network support seems IPv4-only.
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  ASE booted with TCP_NODELAY enabled.
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  Network and device connection limit is 4081.
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  ASE - Dynamic Pluggable Component Interface is disabled
    00:0000:00000:00000:2014/03/21 11:03:41.01 kernel  Adaptive Server is running as process id 25438.
    00:0000:00000:00000:2014/03/21 11:03:41.05 server  Number of blocks left for proc headers: 6920.
    00:0000:00000:00000:2014/03/21 11:03:41.05 server  Proc header memory allocated 1384 pages for each per engine cache.
    00:0000:00000:00000:2014/03/21 11:03:41.05 server  Proc header memory allocated 1384 pages for engine 0 local cache
    00:0000:00000:00000:2014/03/21 11:03:41.05 kernel  Using value of 'number of engines at startup' (1) for size of syb_default_pool.
    00:0000:00000:00000:2014/03/21 11:03:41.05 kernel  Create Thread Pool 3, "syb_blocking_pool", type="Run To Completion", with 4 threads
    00:0000:00000:00000:2014/03/21 11:03:41.05 kernel  Create Thread Pool 2, "syb_system_pool", type="Run To Completion", with 1 threads
    00:0000:00000:00000:2014/03/21 11:03:41.05 kernel  Create Thread Pool 1, "syb_default_pool", type="Engine (Multiplexed)", with 1 threads
    00:0000:00000:00000:2014/03/21 11:03:41.05 kernel  Aggressive task stealing enabled
    00:0000:00000:00000:2014/03/21 11:03:41.05 kernel  Enabling Linux Native Kernel asynchronous disk I/O strategy.
    00:0007:00000:00000:2014/03/21 11:03:41.05 kernel  I/O controller 2 (NetController) is running as task 1127909376 on thread 7 (LWP 25453).
    00:0008:00000:00000:2014/03/21 11:03:41.05 kernel  I/O controller 3 (DiskController) is running as task 1127910096 on thread 8 (LWP 25454).
    00:0000:00000:00000:2014/03/21 11:03:41.05 kernel  Initializing virtual device 0, '/sybase/IB1/sybsystem/master.dat' with dsync 'off'.
    00:0000:00000:00000:2014/03/21 11:03:41.05 kernel  Virtual device 0 started using asynchronous i/o.
    00:0000:00000:00000:2014/03/21 11:03:41.05 server  Loaded default Unilib conversion handle.
    00:0000:00000:00000:2014/03/21 11:03:41.05 kernel  Worker Thread Manager is not enabled for use in ASE.
    00:0000:00000:00000:2014/03/21 11:03:41.05 kernel  Either the config parameter 'use security services' is set to 0, or ASE does not support use of external security mec
    hanisms on this platform. The Security Control Layer will not be initialized. No external security mechanisms will be supported.
    00:0000:00000:00000:2014/03/21 11:03:41.05 kernel  libsybibmmq - Sybase IBM MQ interface/15.7/EBF 21341 SMP SP101 /P/x86_64/Enterprise Linux/ase157sp101/3439/64-bit/OPT
    /Thu Jun  6 12:02:54 2013
    00:0000:00000:00000:2014/03/21 11:03:41.08 kernel  Loaded encryption provider CSI-2.8M2-linuxamd64-2012/12/27 21:15:59 PST-sybcsi_openssl-OpenSSL 1.0.1b 26 Apr 2012.
    00:0000:00000:00000:2014/03/21 11:03:41.08 kernel  Begin processing to generate RSA keypair.
    00:0000:00000:00000:2014/03/21 11:03:41.11 kernel  Completed processing to generate RSA keypair.
    00:0000:00000:00000:2014/03/21 11:03:41.11 kernel  Begin processing to generate RSA keypair.
    00:0000:00000:00000:2014/03/21 11:03:41.28 kernel  Completed processing to generate RSA keypair.
    00:0000:00000:00000:2014/03/21 11:03:41.28 kernel  Encryption provider initialization succeeded on engine 0.
    00:0000:00000:00000:2014/03/21 11:03:41.28 kernel  SSL Plus v5.2.2 security modules loaded successfully.
    --More--(26%)
    00:0006:00000:00000:2014/03/21 11:03:41.28 kernel  Network and device connection limit is 4081.
    00:0006:00000:00000:2014/03/21 11:03:41.28 kernel  ASE - Dynamic Pluggable Component Interface is disabled
    00:0006:00000:00000:2014/03/21 11:03:41.28 kernel  Thread 6 (LWP 25447) of Threadpool syb_default_pool online as engine 0
    00:0006:00000:00000:2014/03/21 11:03:41.28 server  Active traceflags: 1623
    00:0006:00000:00001:2014/03/21 11:03:41.28 kernel  libomni1 - Component Integration Services: using 'Sybase Client-Library/15.7/P-EBF21002 SP100/DRV.15.7.0.10/Linux x86
    _64/Linux 2.6.18-128.el5 x86_64 Native Threads/BUILD1570-026/64bit/OPT/Wed Mar 20 21:34:36 2013'
    00:0006:00000:00001:2014/03/21 11:03:41.28 server  Size of the 16K memory pool: 8192 Kb
    00:0006:00000:00001:2014/03/21 11:03:41.28 server  Opening Master Database ...
    00:0006:00000:00001:2014/03/21 11:03:41.29 server  Loading ASE's default sort order and character set
    00:0006:00000:00001:2014/03/21 11:03:41.29 server  Recovering database 'master'.
    00:0006:00000:00001:2014/03/21 11:03:41.29 server  Started estimating recovery log boundaries for database 'master'.
    00:0006:00000:00001:2014/03/21 11:03:41.29 server  Database 'master', checkpoint=(1634, 132), first=(1634, 132), last=(1634, 173).
    00:0006:00000:00001:2014/03/21 11:03:41.29 server  Completed estimating recovery log boundaries for database 'master'.
    00:0006:00000:00001:2014/03/21 11:03:41.29 server  Started ANALYSIS pass for database 'master'.
    00:0006:00000:00001:2014/03/21 11:03:41.29 server  Completed ANALYSIS pass for database 'master'.
    00:0006:00000:00001:2014/03/21 11:03:41.29 server  Log contains all committed transactions until 2014/03/21 11:03:39.33 for database master.
    00:0006:00000:00001:2014/03/21 11:03:41.29 server  Started REDO pass for database 'master'. The total number of log records to process is 42.
    00:0006:00000:00001:2014/03/21 11:03:41.30 server  Redo pass of recovery has processed 7 committed and 0 aborted transactions.
    00:0006:00000:00001:2014/03/21 11:03:41.30 server  Completed REDO pass for database 'master'.
    00:0006:00000:00001:2014/03/21 11:03:41.30 server  Timestamp for database 'master' is (0x0000, 0x00006ec9).
    00:0006:00000:00001:2014/03/21 11:03:41.30 server  Recovery of database 'master' will undo incomplete nested top actions.
    00:0006:00000:00001:2014/03/21 11:03:41.30 server  Started recovery checkpoint for database 'master'.
    00:0006:00000:00001:2014/03/21 11:03:41.30 server  Completed recovery checkpoint for database 'master'.
    00:0006:00000:00001:2014/03/21 11:03:41.30 server  Started filling free space info for database 'master'.
    00:0006:00000:00001:2014/03/21 11:03:41.30 server  Completed filling free space info for database 'master'.
    00:0006:00000:00001:2014/03/21 11:03:41.30 server  Started cleaning up the default data cache for database 'master'.
    00:0006:00000:00001:2014/03/21 11:03:41.30 server  Completed cleaning up the default data cache for database 'master'.
    00:0006:00000:00001:2014/03/21 11:03:41.30 server  Checking external objects.
    00:0006:00000:00001:2014/03/21 11:03:41.30 server  Database 'master' is now online.
    00:0006:00000:00001:2014/03/21 11:03:41.30 server  The transaction log in the database 'master' will use I/O size of 16 Kb.
    00:0006:00000:00001:2014/03/21 11:03:41.37 server  server is unnamed
    00:0006:00000:00001:2014/03/21 11:03:42.06 server  Configuration file '/sybase/IB1/ASE-15_0/IB1.cfg' has been written and the previous version has been renamed to '/syb
    ase/IB1/ASE-15_0/IB1.001'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Recovering database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Started estimating recovery log boundaries for database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Database 'sybsystemdb', checkpoint=(864, 170), first=(864, 170), last=(864, 170).
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Completed estimating recovery log boundaries for database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Started ANALYSIS pass for database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Completed ANALYSIS pass for database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Log contains all committed transactions until 2014/03/21 11:03:40.01 for database sybsystemdb.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Started REDO pass for database 'sybsystemdb'. The total number of log records to process is 1.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Completed REDO pass for database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Timestamp for database 'sybsystemdb' is (0x0000, 0x0000142f).
    --More--(28%)
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Recovery of database 'sybsystemdb' will undo incomplete nested top actions.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Started recovery checkpoint for database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Completed recovery checkpoint for database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Started filling free space info for database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Completed filling free space info for database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Started cleaning up the default data cache for database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Completed cleaning up the default data cache for database 'sybsystemdb'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Boot Count: 2
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Checking external objects.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  The transaction log in the database 'sybsystemdb' will use I/O size of 16 Kb.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Resident Node id: fb18efb51d00
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Transaction coordinator initialized.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Database 'sybsystemdb' is now online.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Recovering database 'model'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Started estimating recovery log boundaries for database 'model'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Database 'model', checkpoint=(864, 59), first=(864, 59), last=(864, 77).
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Completed estimating recovery log boundaries for database 'model'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Started ANALYSIS pass for database 'model'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Completed ANALYSIS pass for database 'model'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Log contains all committed transactions until 2014/03/21 11:03:39.33 for database model.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Started REDO pass for database 'model'. The total number of log records to process is 19.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Redo pass of recovery has processed 4 committed and 0 aborted transactions.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Completed REDO pass for database 'model'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Timestamp for database 'model' is (0x0000, 0x000013cb).
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Recovery of database 'model' will undo incomplete nested top actions.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Started recovery checkpoint for database 'model'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Completed recovery checkpoint for database 'model'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Started filling free space info for database 'model'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Completed filling free space info for database 'model'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Started cleaning up the default data cache for database 'model'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Completed cleaning up the default data cache for database 'model'.
    00:0006:00000:00001:2014/03/21 11:03:42.07 server  Checking external objects.
    00:0006:00000:00001:2014/03/21 11:03:42.08 server  The transaction log in the database 'model' will use I/O size of 16 Kb.
    00:0006:00000:00001:2014/03/21 11:03:42.08 server  Database 'model' is now online.
    00:0006:00000:00001:2014/03/21 11:03:42.08 server  The logical pagesize of the server is 16 Kb.
    00:0006:00000:00001:2014/03/21 11:03:42.08 server  0 dump conditions detected at boot time
    00:0006:00000:00001:2014/03/21 11:03:42.08 server  Clearing temporary database 'tempdb'.
    00:0006:00000:00001:2014/03/21 11:03:42.09 server  Tempdb 2 is added to the  list of local temporary databases
    00:0006:00000:00001:2014/03/21 11:03:42.09 server  Timestamp for database 'tempdb' is (0x0000, 0x000013ce).
    00:0006:00000:00001:2014/03/21 11:03:42.10 server  The transaction log in the database 'tempdb' will use I/O size of 16 Kb.
    00:0006:00000:00001:2014/03/21 11:03:42.10 server  Database 'tempdb' is now online.
    00:0006:00000:00009:2014/03/21 11:03:42.10 kernel  network name ibssrv02, interface IPv4, address 192.168.2.6, type tcp, port 7905, filter NONE
    00:0006:00000:00001:2014/03/21 11:03:42.10 server  Recovery complete.
    --More--(30%)
    00:0006:00000:00001:2014/03/21 11:03:42.10 server  ASE's default unicode sort order is 'binary'.
    00:0006:00000:00001:2014/03/21 11:03:42.10 server  ASE's default sort order is:
    00:0006:00000:00001:2014/03/21 11:03:42.10 server  'bin_iso_1' (ID = 50)
    00:0006:00000:00001:2014/03/21 11:03:42.10 server  on top of default character set:
    00:0006:00000:00001:2014/03/21 11:03:42.10 server  'iso_1' (ID = 1).
    00:0006:00000:00001:2014/03/21 11:03:42.10 server  Master device size: 400 megabytes, or 204800 virtual pages. (A virtual page is 2048 bytes.)
    00:0006:00000:00001:2014/03/21 11:03:42.10 kernel  Warning: Cannot set console to nonblocking mode, switching to blocking mode.
    00:0006:00000:00001:2014/03/21 11:03:42.10 kernel  Console logging is disabled. This is controlled via the 'enable console logging' configuration parameter.
    00:0006:00000:00015:2014/03/21 11:03:54.09 kernel  Initializing virtual device 1, '/sybase/IB1/sybsystem/sysprocs.dat' with dsync 'off'.
    00:0006:00000:00015:2014/03/21 11:03:54.09 kernel  Virtual device 1 started using asynchronous i/o.
    00:0006:00000:00015:2014/03/21 11:03:55.01 server  Timestamp for database 'sybsystemprocs' is (0x0000, 0x000013ce).
    00:0006:00000:00015:2014/03/21 11:03:55.13 server  Configuration file '/sybase/IB1/ASE-15_0/IB1.cfg' has been written and the previous version has been renamed to '/syb
    ase/IB1/ASE-15_0/IB1.002'.
    00:0006:00000:00015:2014/03/21 11:03:55.13 server  The configuration option 'allow updates to system tables' has been changed by 'sa' from '0' to '1'.
    00:0006:00000:00015:2014/03/21 11:03:55.14 server  Configuration file '/sybase/IB1/ASE-15_0/IB1.cfg' has been written and the previous version has been renamed to '/syb
    ase/IB1/ASE-15_0/IB1.003'.
    00:0006:00000:00015:2014/03/21 11:03:55.15 server  The configuration option 'allow updates to system tables' has been changed by 'sa' from '1' to '0'.
    00:0006:00000:00015:2014/03/21 11:03:55.16 server  Configuration file '/sybase/IB1/ASE-15_0/IB1.cfg' has been written and the previous version has been renamed to '/syb
    ase/IB1/ASE-15_0/IB1.004'.
    00:0006:00000:00015:2014/03/21 11:03:55.16 server  The configuration option 'allow updates to system tables' has been changed by 'sa' from '0' to '1'.
    00:0006:00000:00015:2014/03/21 11:04:22.28 server  Increase the config parameter 'number of open objects' to avoid descriptor reuse. Reuse may result in performance deg
    radation.
    00:0006:00000:00015:2014/03/21 11:04:24.34 server  Configuration file '/sybase/IB1/ASE-15_0/IB1.cfg' has been written and the previous version has been renamed to '/syb
    ase/IB1/ASE-15_0/IB1.005'.
    00:0006:00000:00015:2014/03/21 11:04:24.34 server  The configuration option 'allow updates to system tables' has been changed by 'sa' from '1' to '0'.
    00:0006:00000:00015:2014/03/21 11:04:24.88 server  Configuration file '/sybase/IB1/ASE-15_0/IB1.cfg' has been written and the previous version has been renamed to '/syb
    ase/IB1/ASE-15_0/IB1.006'.
    00:0006:00000:00015:2014/03/21 11:04:24.88 server  The configuration option 'allow updates to system tables' has been changed by 'sa' from '0' to '1'.
    00:0006:00000:00015:2014/03/21 11:04:24.89 server  Configuration file '/sybase/IB1/ASE-15_0/IB1.cfg' has been written and the previous version has been renamed to '/syb
    ase/IB1/ASE-15_0/IB1.007'.
    00:0006:00000:00015:2014/03/21 11:04:24.90 server  The configuration option 'allow updates to system tables' has been changed by 'sa' from '1' to '0'.
    00:0006:00000:00015:2014/03/21 11:04:24.90 kernel  Initializing virtual device 2, '/sybase/IB1/sybsystem/sybsysdb.dat' with dsync 'off'.
    00:0006:00000:00015:2014/03/21 11:04:24.90 kernel  Virtual device 2 started using asynchronous i/o.
    00:0006:00000:00015:2014/03/21 11:04:24.95 server  Configuration file '/sybase/IB1/ASE-15_0/IB1.cfg' has been written and the previous version has been renamed to '/syb
    ase/IB1/ASE-15_0/IB1.008'.
    00:0006:00000:00015:2014/03/21 11:04:24.95 server  The configuration option 'allow updates to system tables' has been changed by 'sa' from '0' to '1'.
    00:0006:00000:00015:2014/03/21 11:04:25.05 server  Configuration file '/sybase/IB1/ASE-15_0/IB1.cfg' has been written and the previous version has been renamed to '/syb
    ase/IB1/ASE-15_0/IB1.009'.
    00:0006:00000:00015:2014/03/21 11:04:25.05 server  The configuration option 'allow updates to system tables' has been changed by 'sa' from '1' to '0'.
    00:0006:00000:00017:2014/03/21 11:04:27.11 kernel  Initializing virtual device 3, '/sybase/IB1/sybtemp/tempdbdev.dat' with dsync 'off'.
    00:0006:00000:00017:2014/03/21 11:04:27.11 kernel  Virtual device 3 started using asynchronous i/o.
    00:0006:00000:00018:2014/03/21 11:04:27.16 server  Configuration file '/sybase/IB1/ASE-15_0/IB1.cfg' has been written and the previous version has been renamed to '/syb
    ase/IB1/ASE-15_0/IB1.010'.
    --More--(32%)
    00:0006:00000:00018:2014/03/21 11:04:27.16 server  The configuration option 'allow updates to system tables' has been changed by 'sa' from '0' to '1'.
    00:0006:00000:00018:2014/03/21 11:04:27.19 server  Configuration file '/sybase/IB1/ASE-15_0/IB1.cfg' has been written and the previous version has been renamed to '/syb
    ase/IB1/ASE-15_0/IB1.011'.
    00:0006:00000:00018:2014/03/21 11:04:27.19 server  The configuration option 'allow updates to system tables' has been changed by 'sa' from '1' to '0'.
    00:0006:00000:00019:2014/03/21 11:04:28.16 server  Configuration file '/sybase/IB1/ASE-15_0/IB1.cfg' has been written and the previous version has been renamed to '/syb
    ase/IB1/ASE-15_0/IB1.012'.
    00:0006:00000:00019:2014/03/21 11:04:28.16 server  The configuration option 'allow updates to system tables' has been changed by 'sa' from '0' to '1'.
    00:0006:00000:00019:2014/03/21 11:04:28.18 server  Configuration file '/sybase/IB1/ASE-15_0/IB1.cfg' has been written and the previous version has been renamed to '/syb
    ase/IB1/ASE-15_0/IB1.013'.
    00:0006:00000:00019:2014/03/21 11:04:28.18 server  The configuration option 'allow updates to system tables' has been changed by 'sa' from '1' to '0'.
    00:0006:00000:00020:2014/03/21 11:04:29.16 server  Configuration file '/sybase/IB1/ASE-15_0/IB1.cfg' has been written and the previous version has been renamed to '/syb
    ase/IB1/ASE-15_0/IB1.014'.
    00:0006:00000:00020:2014/03/21 11:04:29.17 server  The configuration option 'allow updates to system tables' has been changed by 'sa' from '0' to '1'.
    00:0006:00000:00020:2014/03/21 11:04:29.18 server  Configuration file '/sybase/IB1/ASE-15_0/IB1.cfg' has been written and the previous version has been renamed to '/syb
    ase/IB1/ASE-15_0/IB1.015'.
    00:0006:00000:00020:2014/03/21 11:04:29.19 server  The configuration option 'allow updates to system tables' has been changed by 'sa' from '1' to '0'.
    00:0006:00000:00021:2014/03/21 11:04:30.16 server  Configuration file '/sybase/IB1/ASE-15_0/IB1.cfg' has been written and the previous version has been renamed to '/syb
    ase/IB1/ASE-15_0/IB1.016'.
    00:0006:00000:00021:2014/03/21 11:04:30.16 server  The configuration option 'allow updates to system tables' has been changed by 'sa' from '0' to '1'.
    00:0006:00000:00021:2014/03/21 11:04:30.18 server  Configuration file '/sybase/IB1/ASE-15_0/IB1.cfg' has been written and the previous version has been renamed to '/syb
    ase/IB1/ASE-15_0/IB1.017'.
    00:0006:00000:00021:2014/03/21 11:04:30.18 server  The configuration option 'allow updates to system tables' has been changed by 'sa' from '1' to '0'.
    00:0006:00000:00017:2014/03/21 11:04:31.15 server  Configuration file '/sybase/IB1/ASE-15_0/IB1.cfg' has been written and the previous version has been renamed to '/syb
    ase/IB1/ASE-15_0/IB1.018'.
    00:0006:00000:00017:2014/03/21 11:04:31.15 server  The configuration option 'allow updates to system tables' has been changed by 'sa' from '0' to '1'.
    00:0006:00000:00017:2014/03/21 11:04:31.16 server  Configuration file '/sybase/IB1/ASE-15_0/IB1.cfg' has been written and the previous version has been renamed to '/syb
    ase/IB1/ASE-15_0/IB1.019'.
    00:0006:00000:00017:2014/03/21 11:04:31.16 server  The configuration option 'allow updates to system tables' has been changed by 'sa' from '1' to '0'.
    00:0006:00000:00025:2014/03/21 11:04:35.24 server  Shutdown started by user 'sa'. SQL text: shutdown
    00:0006:00000:00025:2014/03/21 11:04:35.25 server  ASE shutdown by request.
    00:0006:00000:00025:2014/03/21 11:04:35.25 kernel  ueshutdown: exiting
    00:0000:00000:00000:2014/03/21 11:04:35.25 kernel  Main thread performing final shutdown.
    00:0000:00000:00000:2014/03/21 11:04:35.30 kernel  Blocking call queue shutdown.
    00:0000:00000:00000:2014/03/21 11:04:35.45 kernel  SySAM: Checked in license for 6 ASE_CORE (2014.1231/permanent/1296 8FE3 0A83 A167).
    00:0000:00000:00000:2014/03/21 11:04:36.50 kernel  SySAM: Using licenses from: /sybase/IB1/SYSAM-2_0/licenses/SYBASE.lic:/sybase/IB1/SYSAM-2_0/licenses/SYBASE

  • Homogeneous System Copy - Installation of Database Instance not possible...

    I try to create a SAP NetWeaver 7.0 SR3 Portal based on a homogeneous SAP System Copy. Therefore I already installed in a first step (first option within SAPINST for installing a target system of a system copy) the Central Services Instance successfully on a machine. In the next step I'd like to create the Database Instance with SAPINST but I cannot choose the DB instance that I already created based on a restore within the new DB server (MS SQL 2008 Cluster installation). I can only choose the local machine for using a DB instance but there is no MS SQL Server installed!
    Do I have to start SAPINST on the DB server itself which is not possible/allowed (due to operating/organization reasons)?
    Is there any SAPINST parameter which I have to use for telling SAPINST that the DB is located on a different server?!?
    The documentation just says:
    The target system is installed using the exports from the source system.
    Choose the installation services exactly in the order they appear. For more information, see the MS SQL Server installation guide for your SAP system at http://service.sap.com/installnw70.
    On the SAPinst screen SAP SystemDatabase make sure to select Homogeneous System Copy (MS SQL Server-specific: Detach/Attach or Backup).
    Thanks for supporting and Regards,
    Claudio Schmidt

    OK, SAP Note 1076022 says:
    SAP installation packages on SAP Service Marketplace
    On March 27, 2008, SAP released the Netweaver installation package SR3, which supports SQL Server 2008 (R2). Note 1152240 discusses the details and lists some restrictions. Make sure you carefully read Note 1152240 and use a recent enough installation master DVD.
    SAP Note 1152240 says:
    If you want to perform a system copy of an SAP system that is based on SAP NetWeaver 7.0 SR3 on SQL Server 2008 (R2), you cannot use the Installation Master and Kernel DVD that you received from SAP or downloaded from SAP Service Marketplace (SMP). Instead, you have to do the following:
    - Patch your runtime libraries as described in SAP note 684106
    - Use a modified Installation Master DVD. For more information, see section "IV Creating a modified Installation Master DVD".
    - Use a modified Kernel DVD. For more information about how to create a modified kernel DVD, see SAP note 1480785.
    What problem is fixed by using the modified Installation Master DVD? Is it possible to install the DB part on a server apart of the local machine where SAPINST is run (my initial question/problem I want do resolve)?
    Regards,
    Claudio

  • Delta Loads failling after system copy with error in source system(RSM340)

    Hi Guru's
    We recently performed system copy in BI side.I am facing same issue in couple of chains.Process chains are failing at delta loads with error in source system(ERROR IN SOURCE SYSTEM-message no-RSM340 ).When I go for repeat option ,delta loads are running fine.I did some research regarding RSM340 and I found note:1576331.
    But my system is not showing any 'Time Inconsistencies'.So.I was not able to find any clue about it.
    Could anybody help  me out in this aspect.
    Thanks!!!
    Kuldeep

    Hi,
    Check whether the profiles that ran in background have the following authorizations.
      The RFC user on BW, receiving data from OLTP system, should have  S_BI-WHM_RFC and S_RS_ALL in the user profile.
    The RFC user on OLTP, receiving request from BW system, should have  S_BI-WX_RFC, S_IDOC_ALL, and, B_ALE_ALL in the user profile.
    Regards .

  • Some errors after doing the system copy for DB2 database instance

    HI,
    Recently we have transferred the DB2 database instance from old host( db 9.1.7 under windows 2003 R2) to new host( DB2 9.7.9 under windows 2008 R2) using the system copy database depending methods.
    Currently system is:
    * ECC 6.0 under NW 7.0 SR3
    * Kernel : 7.20
    * Basis: 7.0 with support package level 17
    *application instance connecting db instance via DB2 CLI
    1)  a) After log in system using the T-code: SM21 to read the system log, it will record the bellow error:
         b)  From the log taken from log fie: dev_w*, i also found the below error:
    A  ABAP Program SAPMSSY2                                .
    A  Source RSBTCTRC                                 Line 60.
    A  Error Code DBIF_RSQL_SQL_ERROR.
    A  Module  $Id: //bas/720_REL/src/krn/runt/absapsql.c#28 $ SAP.
    A  Function ab_HandleRsqlErrors Line 716.
    A  ** RABAX: level LEV_RX_STDERR completed.
    A  ** RABAX: level LEV_RX_RFC_ERROR entered.
    A  ** RABAX: level LEV_RX_RFC_ERROR completed.
    A  ** RABAX: level LEV_RX_RFC_CLOSE entered.
    A  ** RABAX: level LEV_RX_RFC_CLOSE completed.
    A  ** RABAX: level LEV_RX_IMC_ERROR entered.
    A  ** RABAX: level LEV_RX_IMC_ERROR completed.
    A  ** RABAX: level LEV_RX_DATASET_CLOSE entered.
    A  ** RABAX: level LEV_RX_DATASET_CLOSE completed.
    A  ** RABAX: level LEV_RX_ERROR_SAVE entered.
    A  ** RABAX: level LEV_RX_ERROR_SAVE completed.
    A  ** RABAX: level LEV_RX_ERROR_TPDA entered.
    A  ** RABAX: level LEV_RX_ERROR_TPDA completed.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI entered.
    A  ** RABAX: level LEV_RX_PXA_RELEASE_RUDI completed.
    A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP entered.
    A  ** RABAX: level LEV_RX_LIVE_CACHE_CLEANUP completed.
    A  ** RABAX: level LEV_RX_END entered.
    A  ** RABAX: level LEV_RX_END completed.
    A  ** RABAX: end no http/smtp
    A  ** RABAX: end RX_BTCHLOG|RX_VBLOG
    A  SQL error in the database when accessing a table..
    c) any background job will be cancelled when it is running. I think the error is related to above mentioned issue.
    2) If i go to T-code: DB13---Diagnostics----db2 logs,  it will come out the below error:
    Thanks.

    HI Manas,
    Yes, this problem is with particular this table.
    Refer to below error coming from db2diag.log when i access the table:BTCCTL:
    2014-08-12-17.52.08.866000+480 I35784932F1196     LEVEL: Severe
    PID     : 3380                 TID  : 2676        PROC : db2syscs.exe
    INSTANCE: DB2DV1               NODE : 000         DB   : DV1
    APPHDL  : 0-127                APPID: *LOCAL.DB2DV1.140812095207
    AUTHID  : DB2DV1 
    EDUID   : 2676                 EDUNAME: db2agent (DV1) 0
    FUNCTION: DB2 UDB, data management, sqldSetupIndexScan, probe:1873
    MESSAGE : ZRC=0x82040001=-2113667071=SQLD_NONSEVERE_PRGERR
              "non-severe dms programming error"
              DIA8532C An internal processing error has occurred.
    DATA #1 : String, 39 bytes
    Specified index not found for scan open
    DATA #2 : String, 12 bytes
    sqldScanOpen
    CALLSTCK:
      [0] 0x000000018010E989 pdLog + 0x353
      [1] 0x0000000003ABE3C2 sqlzSetAndLog901 + 0x192
      [2] 0x0000000001E61F01 sqldSetupIndexScan + 0xF37
      [3] 0x0000000001E5F5CC sqldScanOpen + 0xBEE
      [4] 0x000000000334F460 sqlriopn + 0x316
      [5] 0x00000000034AE788 sqlritaSimplePerm + 0x252
      [6] 0x000000000336AC8B sqlriSectInvoke + 0x139
      [7] 0x00000000030A6F0C sqlrr_process_fetch_request + 0x1A8
      [8] 0x00000000030A2902 sqlrr_open + 0x534
      [9] 0x000000000223FCCB sqljs_ddm_opnqry + 0x447
    2014-08-12-17.52.08.866000+480 I35786130F533      LEVEL: Error
    PID     : 3380                 TID  : 2676        PROC : db2syscs.exe
    INSTANCE: DB2DV1               NODE : 000         DB   : DV1
    APPHDL  : 0-127                APPID: *LOCAL.DB2DV1.140812095207
    AUTHID  : DB2DV1 
    EDUID   : 2676                 EDUNAME: db2agent (DV1) 0
    FUNCTION: DB2 UDB, data management, sqldSetupIndexScan, probe:1873
    DATA #1 : unsigned integer, 4 bytes
    10
    DATA #2 : unsigned integer, 4 bytes
    1704
    DATA #3 : unsigned integer, 2 bytes

  • System Copy Import Error

    Dear All,
    Good Day
    We are doing a BI Quality System Refresh from our BI Production System.
    we are on Windows 2003 R2 Server & Database MS SQL 2005 Server.
    We followed the Standard System Copy / Migration (Load Based) Installation method.
    We finished the SAP installation positively up to the 13th Phase, while in the "IMPORT ABAP Phase" we are getting the following errors.
    Loading of 'SAPSLOAD' import package: OK
    Import Monitor jobs: running 0, waiting 5, completed 102, failed 10, total 117.
    Import Monitor jobs: running 1, waiting 4, completed 102, failed 10, total 117.
    Import Monitor jobs: running 2, waiting 3, completed 102, failed 10, total 117.
    Import Monitor jobs: running 3, waiting 2, completed 102, failed 10, total 117.
    Loading of 'SAPUSER' import package: OK
    Import Monitor jobs: running 2, waiting 2, completed 103, failed 10, total 117.
    Loading of 'SAPDODS_13' import package: OK
    Import Monitor jobs: running 1, waiting 2, completed 104, failed 10, total 117.
    Loading of 'SAPDODS_6' import package: OK
    Import Monitor jobs: running 0, waiting 2, completed 105, failed 10, total 117.
    Import Monitor jobs: running 1, waiting 1, completed 105, failed 10, total 117.
    Loading of 'SAP0000' import package: OK
    Import Monitor jobs: running 0, waiting 1, completed 106, failed 10, total 117.
    TRACE      2011-05-01 11:58:56.355
    Function setMessageIdOfExceptionMessage: nw.programError
    WARNING[E] 2011-05-01 11:58:56.355
               CJSlibModule::writeError_impl()
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
    TRACE      2011-05-01 11:58:56.433 [iaxxejsbas.hpp:483]
               EJS_Base::dispatchFunctionCall()
    JS Callback has thrown unknown exception. Rethrowing.
    ERROR      2011-05-01 11:58:56.480 [sixxcstepexecute.cpp:950]
    FCO-00011  The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
    TRACE      2011-05-01 11:58:56.527 [iaxxgenimp.cpp:752]
                CGuiEngineImp::showMessageBox
    <html> <head> </head> <body> <p> An error occurred while processing option SAP NetWeaver 7.0 including Enhancement Package 1 Support Release 1 > Software Life-Cycle Options > System Copy > MS SQL Server > Target System Installation > Central System > Based on AS ABAP > Central System. You can now: </p> <ul> <li> Choose <i>Retry</i> to repeat the current step. </li> <li> Choose <i>View Log</i> to get more information about the error. </li> <li> Stop the option and continue with it later. </li> </ul> <p> Log files are written to C:\Program Files/sapinst_instdir/NW701/LM/COPY/MSS/SYSTEM/CENTRAL/AS-ABAP/. </p> </body></html>
    TRACE      2011-05-01 11:58:56.527 [iaxxgenimp.cpp:1255]
               CGuiEngineImp::acceptAnswerForBlockingRequest
    Waiting for an answer from GUI
    *" In The importmonitor log "*_
    INFO: 2011-05-01 11:57:57 com.sap.inst.migmon.LoadTask run
    Loading of 'SAPDODS_6' import package is successfully completed.
    TRACE: 2011-05-01 11:58:26 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is started.
    TRACE: 2011-05-01 11:58:26 com.sap.inst.migmon.LoadTask processPackage
    Task file generation for 'SAP0000' import package:
    K:\usr\sap\FBQ\SYS\exe\uc\NTAMD64\R3load.exe -ctf I E:\Backup\ABAP\DATA\SAP0000.STR "C:\Program Files\sapinst_instdir\NW701\LM\COPY\MSS\SYSTEM\CENTRAL\AS-ABAP\DDLMSS.TPL" SAP0000.TSK MSS -l SAP0000.log -o D
    TRACE: 2011-05-01 11:58:26 com.sap.inst.migmon.LoadTask processPackage
    Loading of 'SAP0000' import package into database:
    K:\usr\sap\FBQ\SYS\exe\uc\NTAMD64\R3load.exe -i SAP0000.cmd -dbcodepage 4103 -l SAP0000.log -loadprocedure fast
    INFO: 2011-05-01 11:58:26 com.sap.inst.migmon.LoadTask run
    Loading of 'SAP0000' import package is successfully completed.
    WARNING: 2011-05-01 11:58:56
    Cannot start import of packages with views because not all import packages with tables are loaded successfully.
    WARNING: 2011-05-01 11:58:56
    10 error(s) during processing of packages.
    INFO: 2011-05-01 11:58:56
    Import Monitor is stopped.
    Kindly Do the needful.
    Thanks in Advance.
    Regards,
    Deepak

    Did you execute the report SMIGR_CREATE_DDL on the source system and copied the resulting SQL files to the database dump directory?
    Markus

  • Export for system copy fails - Error 9 (Bad file number)

    Hello all,
    I am attempting to perform the export phase for a hetergenous system copy on our BI system (BI 7.0 - NW2004s).  This system runs on HP-UX 11.11 using Oracle  10.2.0.2 and will be migrated to Windows Server 2003 and MS SQL Server 2005, once the export is complete.
    While running sapinst to export the data from the source system, there are several input dialog screens that are skipped, which means I am not able to enter all the paramters used for the export.  After seeing this behavior from sapinst, I reviewed the sapinst.log and sapinst_dev.log files and find the warning/error "System call failed. Error 9 (Bad file number)".  I have included a portion of these files below.
    I have reviewed notes 546006 and 583861, but these seem to refer to an Oracle error ORA-27121, but I am not receiving any Oracle errors in sapinst.log or the Oracle alert log.  I have looked for possible permission or ownership problems with any of the SAP or Oracle files, but have not found any that were incorrect.  Also, these errors do not specify which file sapinst is having problems with, so I do not have  a specific file or area to check.
    If anyone has seen something similar to this and has any suggestions, I would greatly appreciate any help.
    sapinst.log details:
    INFO 2009-02-14 15:15:51.67
    Execute step collect of component |NW_Export|ind|ind|ind|ind|0|0|NW_GetSidFromProfiles|ind|ind|ind|ind|1|0|NW_readProfileDir|ind|ind
    |ind|ind|0|0
    INFO 2009-02-14 15:15:52.737
    Account bwpadm already exists.
    WARNING 2009-02-14 15:15:52.747
    System call failed. Error 9 (Bad file number) in execution of system call 'getgrent' with parameter (), line (292) in file (syuxcuse
    r.cpp).
    INFO 2009-02-14 15:15:52.757
    Account 0 already exists.
    WARNING 2009-02-14 15:15:52.777
    System call failed. Error 9 (Bad file number) in execution of system call 'getgrent' with parameter (), line (292) in file (syuxcuse
    r.cpp).
    INFO 2009-02-14 15:15:52.777
    Account 200 already exists.
    WARNING 2009-02-14 15:15:52.827
    System call failed. Error 9 (Bad file number) in execution of system call 'getgrent' with parameter (), line (292) in file (syuxcuse
    r.cpp).
    INFO 2009-02-14 15:16:04.937
    Creating file /tmp/sapinst_instdir/NW04S/LM/COPY/ORA/EXP/CENTRAL/AS/EXP/ypcat.log.
    INFO 2009-02-14 15:16:05.007
    Output of ypcat passwd.byname is written to the logfile ypcat.log.
    sapinst_dev.log details:
    TRACE      2009-02-14 15:15:52.737
    2009-02-14 15:15:52.743 NW._getSAPMount() done: /sapmnt
    INFO       2009-02-14 15:15:52.737 [syuxcaccmg.cpp:227]
               bool CSyAccountMgtImpl::isExisting(ISyAccountMgt::eAccountType accountType, iastring sName)
    Account bwpadm already exists.
    TRACE      2009-02-14 15:15:52.747 [syuxcuser.cpp:1943]
               CSyUserImpl_getOsInfos(ILogBook *m_logBook, iastring sName, iastring sID, tSyUserInfo& msUserinfo)
    getspnam(bwpadm) returned NULL.
    WARNING    2009-02-14 15:15:52.747 [syxxsyshlp.cpp:78]
               syslib::printOSError(const iastring &, int, DWORD, const iastring &, CMessage::eLogMessage)
    System call failed. Error 9 (Bad file number) in execution of system call 'getgrent' with parameter (), line (292) in file (syuxcuse
    r.cpp).
    Regards,
    Rusty Robbins

    Hello Peter,
    Thanks for the reply. I did confirm the points you made, and have the details below.
    1. check filesystem, if you have enough space, especially /tmp
    All filesystems have available space, and /tmp has 310 MB available, before the start of sapinst.
    2. check again alert log, trace log for Oracle,
    I could not find any errors in the alert_SID.log or any unusual trace files.
    3. How did you run sapinst? Are you using "root" account.
    I am running sapinst as user root and I am following all the recomendations in the system copy guide (at least as far as I can tell.  ;p )
    We have four BI systems in this landscape, and the other three have migrated successfully.  The procedure I am using, is the same as for the other 3 systems and uses the same SAP media directory that was used on the other systems.
    One other item that may be part of my problem here, is that this system is the production system, and was originally installed as a high-availability system, using HP-UX Service Guard for clustering.  Currently, this system does not have fail-over enabled, but of course the cluster is still intact.  One required piece of the Service Guard enviornment is the use of a virtual hostname.  This seems to resolve successfully by sapinst, as I see the correct (virtual) hostname referenced several times.  While this is a clustered system (for fail-over purposes), the CI and DB are installed on the same host.  So it is not a distributed system, and if failover had been initiated, it would fail both the CI and DB instance, which is the same and only SAP instance.
    This did raise one question in my mind, however.  I am attempting to extract this using the following menu path within sapinst.
    SAP NetWeaver 7.0 Support Release 3  --> Software Life-Cycle Options --> System Copy --> Oracle --> Source System Export --> Central System --> Based on AS ABAP and AS Java
    Since this does use Service Guard, but is not a distributed system, should I be using a different path in the sapinst tree, for the export?  I have only performed a migration using the above path, so I am not familar with the detailf of the other types, such as High-Availabitly or Distributed-System.
    Regards,
    Rusty

  • System copy - Export Error

    Hi all,
    While i was trying export ABAP + JAVA based system using system copy (Central System), i am getting below error in sapinst.log....
    I am able connect ConfigTool without any issues
    I did reset the password for jdbc  in the configtool secureStore and DB site (SQL Server)
    <!LOGHEADER[END]/>
    Mar 3, 2010 3:24:05 AM   Info   : Successfully parsed!
    Mar 3, 2010 3:24:05 AM   Info   : Executing command Export...
    Mar 3, 2010 3:24:05 AM   Info   : Establishing DB connection...
    Mar 3, 2010 3:24:07 AM   Path   : Exception : The DataBase is down or the connection parameters are wrong: -sid=<SID> -dsn=jdbc/pool/<SID> -ssprops=D:/usr/sap/<SID>/SYS/global/security/data/SecStore.properties -ssk=D:/usr/sap/<SID>/SYS/global/security/data/SecStore.key -keyphrase=null
    java.lang.Exception
    Note - I replaced my actually SID name with <SID>
    Any help highly appreciated.
    -Sekhar

    YES, system is up and running.
    I used our SQL Enterprise Mananger and was able to connect to the database.
    FYI...
    System running with 2004s dual stack, MS SQL Server 2005, 32bit build
    -sekhar

  • System Copy - Homogenous and Heterogeneous

    Hi All Experts,
    Could one of you, please explain me the steps how to performed Homogenous,
    Heterogeneous, Client copy and System copy. Please help.
    Thanks,
    Frank.

    Hi Frank,
    For client copy there are two types one is Local client copy which is with the system and Remote client copy which is copy of client from one system to another system.
    Local client copy :
         1. scc4 .. entry for new client
         2. logon to the new entered client with SAP* password: pass
         3. sccl ..select source client and target would the one u logged in currently.
         4. Set the parallel processes ( depends on u r cpu) normally 6 -16
         5. Start in dialog
         6. check the logs in SCC3 .
    Remote client copy:
    1. Scc4 entry for the client.
      2. SCC8 RFC maintain .. folow the screens
      3. Scc3
    System Copy:
    1. Take the offline backup of the source system and the control file.
    2. Restore the backup on the target system.
    3. change the control file path.
    4. change in the control file where this RESET to SET
    5. Startup database in mount state.
    6. Run the control file.
    7. open the database with command : alter database open resetlogs;
    8.All Done !!!
    I hope its helpfull ..

  • IDES system copy ..error during IMPORT_ABAP..unable to create indexes

    Hi all,
    I am doing a IDES system copy. I ran the report SMIGR_CREATE_DLL , the export activities have been completed successfully as well on the source system. Now on the target system, during the import, I am getting the following error in the log file SAPDFACT.log.
    (DB) ERROR: DDL statement failed
    (CREATE  INDEX "/BI0/E0RSTT_C06~P" ON "/BI0/E0RSTT_C06" ( "KEY_0RSTT_C06P" , "KEY_0RSTT_C06T" , "KEY_0RSTT_C06U" , "KEY_0RSTT_C061" , "KEY_0RSTT_C062" , "KEY_0RSTT_C063" , "KEY_0RSTT_C064" , "KEY_0RSTT_C065" , "KEY_0RSTT_C066" , "KEY_0RSTT_C067" , "KEY_0RSTT_C068"  ) TABLESPACE PSAPSR3 STORAGE (INITIAL 65536 NEXT 0000002560K MINEXTENTS 0000000001 MAXEXTENTS 2147483645 PCTINCREASE 0 ) NOLOGGING COMPUTE STATISTICS )
    DbSlExecute: rc = 99
      (SQL error 1408)
      error message returned by DbSl:
    ORA-01408: such column list already indexed
    (DB) INFO: disconnected from DB
    The owner for this table is SAPSR3. Some oracle forums suggested to drop the index before recreating it. But when i do "drop index SAPSR3."/BI0/E0RSTT_C06~P..it says.."the specified index does not exist". But when I go to recreate this index, it doesn get created successfully. After that when I re-run the import, it again fails. Suprisingly..now if i go to check if this index is present thru a sql querry:
    select owner, object_name, object_type from dba_objects where object_name='SAPSR3."/BI0/E0RSTT_C06~P"', it tells "no rows selected". This is happening everytime, I create an index, where it gets created successfully, and the import again fails with the same error in SAPDFACT.log.
    I found an SAP note 885441 named..common errors during migration..although mine isnt a migration..my both source and destination are Red hat 64 bit platform.
    The note 1st asks to download the latest R3load..which I did and extracted in the kernel directory of the source..then it also asked to edit the .TSK file..in my case..SAPDFACT.TSK..where the lines:
    I /BIC/E<Cubename>~<index> C err
    to  I /BIC/E<Cubename>~<index> C ign..
    I did that..this time..the import again fails..but in the SAPDFACT.log..it complains about some other index..n the same gets generated in the .TSK file as well..the earlier index error is not again generated.
    I am not sure..what is going wrong..my export went through successfully.i have done the prep steps for export as well..before that i ran the SMIGR_CREATE_DLL report as well..
    Any inputs are highly appreciated..
    Thanks,
    Akshay

    Hi,
    Check SAP  Note 1166589 - Table converter: DB error when creating secondary indexes
    Thanks
    Sunny

  • After system copy facing error in DBACOCKPIT

    Dear All
    We are installing QAS server through system copy from DEV server.But after installtion when we run transction it's give us errors.
    Wed Aug 17 15:44:29 2011
    M  ThEMsgArrived: sysmsg_for_rfc = 0
    B  Connect to +++DB6ADM as DB2DEV with DB6_DB_NAME=QAS;DB6_DB_SCHEMA=SAPQAS
    C  *** ERROR in DB6Connect[dbdb6.c, 1792] CON = 1 (BEGIN)
    C  &+     DbSlConnectDB6( SQLConnect ): [IBM][CLI Driver] SQL1060N  User "DB2DEV  " does not have the CONNECT privilege.  SQ
    C  &+     LSTATE=08004                                                                               
    C  &+                                                                               
    C  &+                                                                               
    C  &+     ABAP location info 'CL_SQL_CONNECTION=============CP', 334                                                       
    C  &+     SAP user 'SM_IBM', transaction code 'DBACOCKPIT'                                                                 
    C  &+                                                                               
    C  *** ERROR in DB6Connect[dbdb6.c, 1792] (END)
    C  *** ERROR => DbSlConnect to 'QAS' as 'DB2DEV' failed
    [dbdb6.c      1797]
    C  {root-id=0050563700011ED0B297BB2AFD244193}_{conn-id=00000000000000000000000000000000}_0
    B  ***LOG BY2=> sql error -1060      performing CON        [dbds         902]
    B  ***LOG BY0=> SQL1060N  User "DB2DEV  " does not have the CONNECT privilege.  SQLSTATE=08004 [dbds         902]
    B  ***LOG BY1=> sql error -1060      [dbacds       1496]
    B 
    B Wed Aug 17 15:44:30 2011
    B  Connect to +++DB6ADM as DB2DEV with DB6_DB_NAME=QAS;DB6_DB_SCHEMA=SAPQAS
    C  *** ERROR in DB6Connect[dbdb6.c, 1792] CON = 1 (BEGIN)
    C  &+     DbSlConnectDB6( SQLConnect ): [IBM][CLI Driver] SQL1060N  User "DB2DEV  " does not have the CONNECT privilege.  SQ
    C  &+     LSTATE=08004                                                                               
    C  &+                                                                               
    C  &+                                                                               
    C  &+     ABAP location info 'CL_SQL_CONNECTION=============CP', 334                                                       
    C  &+     SAP user 'SM_IBM', transaction code 'DBACOCKPIT'                                                                 
    C  &+                                                                               
    C  *** ERROR in DB6Connect[dbdb6.c, 1792] (END)
    C  *** ERROR => DbSlConnect to 'QAS' as 'DB2DEV' failed
    [dbdb6.c      1797]
    C  {root-id=0050563700011ED0B297BB2AFD244193}_{conn-id=00000000000000000000000000000000}_0
    B  ***LOG BY2=> sql error -1060      performing CON        [dbds         902]
    B  ***LOG BY0=> SQL1060N  User "DB2DEV  " does not have the CONNECT privilege.  SQLSTATE=08004 [dbds         902]
    B  ***LOG BY1=> sql error -1060      [dbacds       1496]
    B  Connect to +++DB6ADM as DB2DEV with DB6_DB_NAME=QAS;DB6_DB_SCHEMA=SAPQAS
    C  *** ERROR in DB6Connect[dbdb6.c, 1792] CON = 1 (BEGIN)
    C  &+     DbSlConnectDB6( SQLConnect ): [IBM][CLI Driver] SQL1060N  User "DB2DEV  " does not have the CONNECT privilege.  SQ
    C  &+     LSTATE=08004                                                                               
    C  &+                                                                               
    C  &+                                                                               
    C  &+     ABAP location info 'CL_SQL_CONNECTION=============CP', 334                                                       
    C  &+     SAP user 'SM_IBM', transaction code 'DBACOCKPIT'                                                                 
    C  &+                                                                               
    C  *** ERROR in DB6Connect[dbdb6.c, 1792] (END)
    C  *** ERROR => DbSlConnect to 'QAS' as 'DB2DEV' failed
    [dbdb6.c      1797]
    C  {root-id=0050563700011ED0B297BB2AFD244193}_{conn-id=00000000000000000000000000000000}_0
    B  ***LOG BY2=> sql error -1060      performing CON        [dbds         902]
    B  ***LOG BY0=> SQL1060N  User "DB2DEV  " does not have the CONNECT privilege.  SQLSTATE=08004 [dbds         902]
    B  ***LOG BY1=> sql error -1060      [dbacds       1496]
    B  Connect to +++DB6ADM as DB2DEV with DB6_DB_NAME=QAS;DB6_DB_SCHEMA=SAPQAS
    C  *** ERROR in DB6Connect[dbdb6.c, 1792] CON = 1 (BEGIN)
    C  &+     DbSlConnectDB6( SQLConnect ): [IBM][CLI Driver] SQL1060N  User "DB2DEV  " does not have the CONNECT privilege.  SQ
    C  &+     LSTATE=08004                                                                               
    C  &+                                                                               
    C  &+                                                                               
    C  &+     ABAP location info 'CL_SQL_CONNECTION=============CP', 334                                                       
    C  &+     SAP user 'SM_IBM', transaction code 'DBACOCKPIT'                                                                 
    C  &+                                                                               
    C  *** ERROR in DB6Connect[dbdb6.c, 1792] (END)
    C  *** ERROR => DbSlConnect to 'QAS' as 'DB2DEV' failed
    [dbdb6.c      1797]
    C  {root-id=0050563700011ED0B297BB2AFD244193}_{conn-id=00000000000000000000000000000000}_0
    B  ***LOG BY2=> sql error -1060      performing CON        [dbds         902]
    B  ***LOG BY0=> SQL1060N  User "DB2DEV  " does not have the CONNECT privilege.  SQLSTATE=08004 [dbds         902]
    B  ***LOG BY1=> sql error -1060      [dbacds       1496]
    B 
    B Wed Aug 17 16:12:36 2011
    B  Connect to +++DB6ADM as DB2DEV with DB6_DB_NAME=QAS;DB6_DB_SCHEMA=SAPQAS
    C  *** ERROR in DB6Connect[dbdb6.c, 1792] CON = 1 (BEGIN)
    C  &+     DbSlConnectDB6( SQLConnect ): [IBM][CLI Driver] SQL1060N  User "DB2DEV  " does not have the CONNECT privilege.  SQ
    C  &+     LSTATE=08004                                                                               
    C  &+                                                                               
    I can't understand we are installed QAS server why it's show User "DB2DEV   for connection
    I am also oracle DBA but new in DB2
    Please guide me
    Regards

    Hi,
    It might be helpful for you to check the SAP note 1072206 and change administration connection accordingly.
    Regards,
    Masako

Maybe you are looking for

  • Album artwork shows up in itunes but not on the ipod...

    i just realized when i put some new songs on my ipod that not the album artwork werent showing up, so i followed some directions i found in some other discussion threads, like unchecking the display artwork button and checking it again. But instead o

  • ESB -- Routing the fault

    hi, I am new to ESB development. Please share your thoughts on the following: 1. When I register a new/modified ESB process, a dialogbox with the below message comes up, if ok is clicked then shows the Registration Summary window with service registr

  • Ocfs2 problem with heartbeating

    I'm trying to setup 2 SUSE10 boxes with iscsi and ocfs2. I installed and configured ocfs2-1.1.1 and the tools for that version. I am able to start ocfs2 and mount the fs. But on 1 of the nodes, the /var/log/messages is showing this: Mar 21 19:46:28 t

  • Modify SRM Inbox

    Hi Experts, I have to modify my SRM inbox with new custom attributes. I have seen one blog which explains how to add custom attribute but my req is to add one new custom attribute which is not available in BOR object Regards, Jacob

  • HT204053 How do I get another persons photos on my iCloud

    Howdo I get another persons iCloud photos on my iCloud