Homogenous Distrubuted Database.

what is the best practise to insert the records in Homogenous distrubuted Environment.
example i have 3 database whenever any dml transaction happens on one i want to update the other databases also...
I was thinking for the dblink to preform this task... but want to know the best practise to do the same...
waiting for response...

Thanks for your reply...
I am having three office at three different location generally they use they office information only but sometime they want to other offices information too...
and I don't want one database forthis...
What i was thinking...
create three database and install server at each office and whenever any transaction happens i want to insert into other two database also...
I don't want to implement dataguard... if I do this on 10g then i cannot pass any transaction against the data guard db that's why i was thinking to create a dblink to push the data to other database with simple insert command in after insert trigger.... but iam not sure whether this is the correct away of doing ?

Similar Messages

  • 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

  • HI i am a Basis Guy.

    I want to about EP6.0 and  EP7.0. can any one give me the introduction to them and abt installation as well. if possible any one can provide cam shots as well

    Hi Sreekanth
    Combination of SAP systems, which must be installed on homogeneous platforms (database, operating system, and hardware)
    An SAP installation consists of SAP systems, usually production, test, and training or development systems. A maximum of eight production systems can be operated under one installation. If you have any additional production systems, you must request a new installation from your SAP contracts department.
    The customer must register a separate installation in writing with SAP for each software product. SAP will then give you a unique installation number.
    Installation
    You can find the SAP Web AS installation guide on SAP Service Marketplace at service.sap.com/installNW2004s ® Installation.
    Configuration Steps Following Installation
    To use certain functions, you need to carry out certain procedures after the installation of the SAP Web AS. For more information, see Post Installation
    Procedures.
    Applying for and Installing the SAP License
    When you first install a J2EE-only installation of the SAP Web AS, you get a temporary license. You have to apply for a permanent license from SAP and install it. For more information, see Licensing the J2EE Engine.
    Ports
    For more information about J2EE Engine ports, see J2EE Engine Ports.
    Rgds
    Srikanth

  • MSSQL Homogeneous System Copy : SAPINST cannot connect to default database

    Hello.
    We want to perform a homogeneous system copy, following Note 151603.
    We have attached the source DB (RP1) to the destination DB (RD4) following the above mentioned Note.
    Now, logged to the server as DOMAIN\rd4adm , we want to execute the SAPINST, as indicated in the Note 683447, but when giving the password for user rd4adm we get a pop up
    Cannot connect to R3SVIL\RD4 [SQL Server]Cannot open user default database. Login failed.
    R3SVIL is the server. Login is done with windows authentication (connected as domain\rd4adm)
    We cannot find a Note descibing this issue and how to fix it, must be something with user : does anybody have suggestion or solution?
    Thanks a lot,
        Dino

    Hi,
    did you apply SAP note 551915 - R/3 won't start after database restore or database copy
    also check Note 806925 - SQL Error 4064: Cannot open user default database
    regards,
    kaushal

  • 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

  • Help !!! Homogeneous system copy hold on step: Create Database

    Group,
    we use homogeneous system copy to install PRD system. The system hold on step : create databse.
    When we check the server and found the data library has been restored from tape. The installation just hold on the step and can't going on.  And there is not additional information on install directory except to see the file keydb.xml were updated.
    Could we adjust the file keydb.xml to continue the installation ? If we could, how ? Thanks in advance.
    Regards.
    Jenny

    Hi Jenny,
    The first question would be:
    Is the database restored properly ?
    How many objects are in there ?
    First stop the SAPinst program so that no "duplicate updates" happen on the log/xml files.
    Most likely you are doing this on another server and therefore the old users are not available which creates an error during restore. This causes often/always an abnormal end of the SAPinst.
    If this is the case, you might want to check the keydb.xml after that you copied that and search for "ERROR" in uppercase and the finally try to set this to OK. If you then rerun SAPinst, this problem is hopefully solved. Unfortunately this is more or less an "standard-error" in this procedure - at least up to 1 year ago I don't know on any generic solution. That's why I do not use this procedure if not really necessary.
    Regards
    Volker Güldenpfennig
    P.S.: Do not forget to distribute forum points as in the last questions - otherwise, you will receive less and less answers ...

  • Homogeneous Database copy without tape restoration

    Hi all,
    I have AIX 5.3 servers with Oracle as databse. I am supposed to do database copy on a new server from an already existing server. However there ios no tape connectivity to that server. But both the servers are on same SAN. How is it possible to do database copy. Both would be same OS and same Database. Please tell me what are the steps to be taken for database copy.
    Regards,
    Priya

    Hi,
    Do the following:
    1. Take Latest Offline/Online Oracle DB Backup of that Source System, from which you want to copy DB.
    2. Copy that Offline/Online Oracle DB Backup Fille and Backup log file (*.anf) of that Source System to the Target System, on its free available local disk space.
    3. Perform Homogeneous System Copy using Oracle DB Restore method:
         3.1 Restore Target Oracle DB using that Source Oracle DB with the help of BRRESTORE command.
         3.2 Backup Control Files from Source System and Change it according to the Target System directory structure before applying to to Target System.
         3.3 Perform Recovery using available Offline redo-log files (if you have restored Online Backup)
    All above mentioned steps are well described in this useful document "[Homogeneous System Copy using Online/Offline Database Backup|http://www.basisconsultant.com/component/remository/Sytem-Copy-Guides/Homogeneous-System-Copy-using-OnlineandOffline-Backup/]" with proper understanding. Download it with simple registration and Please read it carefully and follow the steps mentioned in that guide.
    Upon error, post your message.
    Regards,
    Bhavik G. Shroff

  • Can TDMS be used to do homogeneous database copy?

    I raise this question is that for our tarabyte size DB, BDLS is too long (days!).
    I know TDMS is also slow, however BDLS can be avoid.
    We want to try TDMS for homogeneous DB copy -- change SID during copy. Is it possible and feasible?
    Please help input your opinions.
    Thanks!

    Hello David,
    TDMS has its own internal logic of selecting the data (table entries) based on the from date you might choose and hence it gurantees the consistenct transfer of data from one system (possibly your production or quality system) to the other system.
    But you can't use this copy for the production use.
    SAP TDMS is not a generic data transfer tool. It is designed exclusively for building up nonproduction
    systems (test systems, training systems etc.) and for refreshing the data in systems built
    up by means of SAP TDMS. It even includes a specific check for making sure that the target
    system is not flagged as a production system.
    So the answer to both the question will be NO. you can't use the reduced data system to productive use.
    Best Regards
    Niraj

  • Failure during database recovery on Homogeneous System Copy

    Dear all,
    i am trying to do system copy, and it fails after the execution step:  database recovery
    MaxDB: 7.6.5.15
    SAP Netweaver 7 Ehp 1
    apparantly this is something to do with LOAD_SYSTAB.
    I could run load_systab [-u <sysdba_user>,<sysdba_user_password>] manually, but the Log file of SAPinst shows the following:
    WARNING[E] 2009-09-28 17:17:57.328
               CJSlibModule::writeError_impl()
    The dbmcli call for action LOAD_SYSTAB failed. SOLUTION: Check the logfile XCMDOUT.LOG.
    TRACE      2009-09-28 17:17:57.546 [iaxxejsbas.hpp:408]
               handleException<ESAPinstJSError>()
    Converting exception into JS Exception EJSException.
    TRACE      2009-09-28 17:17:57.562
    Function setMessageIdOfExceptionMessage: dbmodada.actorext.dbmcliCallFailed
    WARNING[E] 2009-09-28 17:17:57.562
               CJSlibModule::writeError_impl()
    The dbmcli call for action LOAD_SYSTAB failed. SOLUTION: Check the logfile XCMDOUT.LOG.
    TRACE      2009-09-28 17:17:57.562 [iaxxejsbas.hpp:483]
               EJS_Base::dispatchFunctionCall()
    JS Callback has thrown unknown exception. Rethrowing.
    ERROR      2009-09-28 17:17:57.781 [sixxcstepexecute.cpp:950]
    FCO-00011  The step sdb_instance_load_systables 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_CreateDB|ind|ind|ind|ind|0|0|NW_ADA_DB|ind|ind|ind|ind|6|0|SdbPreInstanceDialogs|ind|ind|ind|ind|4|0|SdbInstanceDialogs|ind|ind|ind|ind|1|0|SDB_INSTANCE_CREATE|ind|ind|ind|ind|0|0|sdb_instance_load_systables was executed with status ERROR .
    TRACE      2009-09-28 17:17:58.93 [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 > MaxDB > 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/ADA/SYSTEM/CENTRAL/AS-ABAP/. </p> </body></html>
    TRACE      2009-09-28 17:17:58.109 [iaxxgenimp.cpp:1255]
               CGuiEngineImp::acceptAnswerForBlockingRequest
    Waiting for an answer from GUI
    XCMDOUT.LOG shows only the SAP users data from the source system, and not for the target system which is having the error.
    Could somebody please advise me what to do?
    Thank you,
    Mariana

    Dear Christian,
    yes, I solved this LOAD_SYSTAB problem.
    This is what I did:
    1. check XCMDOUT.LOG
    2. However in my case, I did not see any clue there, so I read this link about LOAD_SYSTAB http://maxdb.sap.com/doc/7_7/45/11cbd6459d7201e10000000a155369/content.htm
    I tried it manually, and it worked: dbmcli u2013d <DB_ID> u2013u DBMUser,password1 load_systab u2013u superdba,password2
    From there, I know that I entered the wrong SYSADM User (superdba) password, this password was in my case the same one a SAPinst Master Password.
    According to https://websmp130.sap-ag.de/sap(bD1kZSZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=25591
    a new installation of MaxDB database, by default, the credential for SYSADM is: "superdba,admin"
    So, accordingly, the solution is:
    change the SYSADM for the <DB_ID> in DBMGUI: D7D - Configuration - Database User area, exactly as the SAPinst Master Passwort.
    Hope this helps.
    Regards,
    Mariana

  • Homogeneous system copy using database specific tools

    My enviroment is ECC6/Oracle 10.2.0.2/Solaris 10
    I'm attempting my first system copy (central instance ABAP) using database specific tools from my PRD to my QAS system
    in the source system I ran sapinst and proceed as follows
    Execution of Service SAP ERP 6.0 SR3 > Software Life-cycle options > system copy > oracle >  source system export >
    central system > based on AS ABAP ? Database Instance Export
    The export creates two folders and an file  ie ABAP, JAVA & LABELIDX.
    The folder ABAP is empty while JAVA has three files.see details below.  I have a feeling something is not right  ?
    Kindly advice before I proceed with database offline backup and importation in the target system
    */oracle/INSTDIR/MIGRATION-CD/SYSCOPY*
    *root@PRD#*
    *root@PRD#*
    *root@PRD#ls -l*
    *total 6*
    *drwxrwxr-x   2 root     sapinst      512 Jul 12 13:19 ABAP*
    *drwxrwxr-x   2 root     sapinst      512 Jul 12 13:19 JAVA*
    *-rw-rw-r--   1 root     sapinst       10 Jul 12 13:19 LABELIDX.ASC*
    *root@PRD#*
    *root@PRD#cd ABAP*
    *root@PRD#ls -l*
    *total 0*
    *root@PRD#*
    *root@PRD#cd ../JAVA*
    *root@PRD#pwd*
    */oracle/INSTDIR/MIGRATION-CD/SYSCOPY/JAVA*
    *root@PRD#ls -l*
    *total 6*
    *-rw-rw-r--   1 root     sapinst       19 Jul 12 13:19 LABEL.ASC*
    -rw-r-----   1 root     sapinst       14 Jul 12 13:19 LABELIDX.ASC
    -rw-r-----   1 root     sapinst      168 Jul 12 13:19 SOURCE.PROPERTIES
    root@PRD#
    root@PRD#     
    According to the system copy documents I've gone through I expect to see the following
    in the  export directory
    => structure with label files and source system information
    => database structure files (*.STR) for ABAP database objects
    => database statistics
    => Size calculation for the target database (*.EXT, DBSIZE.XML)
    => Archiving of the SDM
    => Archiving of  application specific file system content
    I get a dialog box message that the export has completed successfullu but only two phases were done ie
    => NW_export
    => Prepare To export Java

    Thanks Mark
    I'll proceed with the import & inform you about the outcome
    My QAS system is the transport domain controller i.e. it hosts the transport directory /usr/sap/trans
    What happens to pending transports after system copy ? Is there a way I can retain them or do I have to advice my users to complete pending requests so that I can import all of them before proceeding .
    what happens to the CUA configurations in my 3 tier system landscape after I overwrite QAS ? I will make a note of all the RFC's & thier configuration details just incase I need to recreate them
    Regards

  • Homogeneous Database Copy

    Hi,
    I am currently doing the process above using a tool supplied by SAP.
    For example:
    Source SID = DEV
    Source DB  = MSSQL 2000
    Source OS  = Windows 2000 Advan Server
    R/3        = 4.7, 640
    Target System is as above but lets put the SID as QAS.
    By using the tool, i need to key in the Abap RFC User
    and password in one of the dialog process.i wish i could attach the print screen but unfortunately.Instead the OSS note which describe the tool is 683447.I have tried SAP*, DDIC and even a user with SAP_ALL profile but still does not work.Any advice is appreciated.
    Cheers..

    Hi Danny,
    Not that I have worked on the tool but still want to try if I can get the issue resolved.
    As I can see, this message was posted some time back, so first of all want ot know if the problem still persist.
    If yes, please also send us the error message you are getting while performing the migration.
    Regards,
    Vineet

  • 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

  • Resoring prodution database into new installed sap system

    have installed ecc 6.0 with sql server 2008 (sp 1) on windows 2003
    server with 64 bit.
    My installtion was done sussfully and also i started sap system.It
    was working fine. then i took backup from my standalone system .
    I restored prodution server database in standalone system and restore
    was done successfully.
    Then iam trying to login to sap system then it was saying that
    dispature was stopped.
    first dispatur was in yellow and status running message server
    connection ok,dialuge que time 0;00sec,j2ee status info unavailable.
    Iam sending screen shots and also related error log files attatched.
    Please can you get help from those documents.
    I also checked r3trans -d.
      C:\Documents and Settings\Administrator>r3trans -d
    This is r3trans version 6.14 (release 700 - 12.06.09 - 15:20:00).
    unicode enabled version
    2EETW169 no connect possible: "DBMS = MSS  ---  SERER = 'SHURJO' DBNAME = 'PRD'"
    r3trans finished (0012).
    before doing  prodution database restore is compulsary to i have to increase the patch levels of my new installed system
    because my prodution server abap& basis patch levels are 19 and my installed system it is only 14.
    Please can any body give right way to resolve this problem,
    Regards,
    Krishna

    >  before doing  prodution database restore is compulsary to i have to increase the patch levels of my new installed system
    >  because my prodution server abap& basis patch levels are 19 and my installed system it is only 14.
    First: It's pointless to first install a full system and then try to overwrite the database with another one.
    I would INSTALL the system using the database copy.
    This procedure is call "homogeneous system copy" and there's a guide for that available at http://service.sap.com/instguides and also in "Note 151603 - Copying an SQL Server database".
    The error message is coming because the database has not the proper users, you'd need to run the STM tool to adapt the users and the environment. Those steps are all described in detail in the guide.
    Markus

  • Licecache table missing Table MATRIXINDE does not exist in the database wit

    Hello,
    We recently done a system copy of our APO system, everything went well. in case of Livecache there are 2 problem
    1) when we do the integration for LCA/LDA/LCA while we mentione the Livecache server it is not taking the host name , it is only picking the IP address of the livecache server. If we tried host name, it times out.
    2) once we give the IP address as livecache server  we can start the live cache server. Bure there is only two tables in it
    when we run
    transaction Livecache Check (/SAPAPO/OM03) we get the erro i.e.Table MATRIXINDE does not exist in the database with ID LCA
    runtime error DBIF_RSQL_TABLE_UNKNOWN
    When we look into the tables there are only 2 tables in it
    AAPSYSNAME
    LCA_WARNINGS
    when I compare with other system...it is missing a lots of other tables..
    We did re-initialized the livecache.
    Appreciate your help in this

    Hello Sudhir,
    1) Did you create the SAP ticket where this issue is reported?
    2) It's good to know more details about the APO version, liveCache/LCA versions on your
        source & target systems.
        What note or document did you follow to do a system copy of our APO system?
    3) Please pay attention to the recommendations in the SAP notes:::
             877203     Post steps after the Homogenous liveCache copy usi u2026
             886103    System Landscape Copy for SAP SCM
    Thank you and best regards, Natalia Khlopina

  • Authority issues after homogeneous system copy - as/400 v5r1 - R/3 4.6C

    Hello,
    I am trying to complete a homogeneous system copy of an R/3 system.
    The source system is PRD - the target system is TST.  The hardware platforms are different (both iSeries) but the kernel/pdf/OS patch levels are all identical.
    The process I have follow so far is this:
    1. Preprocessing of the R3PRDDATA library.
    2. SAVLIB of R3PRDDATA.
    3. Delete old R3TSTDATA lib on target system using QSECOFR
    4. Create new R3TSTDATA using SQLUTIL as TSTOFR (TSTOFR is my user for the target system)
    5. CHGOBJOWN OBJ(R3TSTDATA) OBJTYPE(*LIB) NEWOWN(TSTOFR)
    6. GRTOBJAUT OBJ(R3TSTDATA) OBJTYPE(LIB) USER(SAP02) AUT(CHANGE)
    7. Detach existing Journal, create new journal receiver, create new journal ...
    DLTJRN JRN(R3TSTDATA/QSQJRN)
    DLTJRNRCV JRNRCV(R3TSTJRN/QSQJRN0001)
    CRTJRNRCV JRNRCV(R3TSTJRN/QSQJRN0001) THRESHOLD(500000)
    CHGOBJOWN OBJ(R3TSTJRN/QSQJRN0001) OBJTYPE(*JRNRCV) NEWOWN(R3OWNER)
    CRTJRN JRN(R3TSTDATA/QSQJRN) JRNRCV(R3TSTJRN/QSQJRN0001) MNGRCV(SYSTEM) DLTRCV(NO)
    CHGOBJOWN OBJ(R3TSTDATA/QSQJRN) OBJTYPE(*JRN) NEWOWN(R3OWNER)
    8. RSTLIB from tape.
    9. AS4FIXFILE on R3TSTDATA with
       DBLIB         R3TSTDATA
       CHGOWN   *NO
       ENDJRN      *YES
       STRJRN      *YES
       CHGFILE     *NO
    10. install license key
    So from this point the system will start without a problem.  However whenever I try and write something to the database I get this type of error (via SM21 or ABAP dump) message:
    ‘Database error -551 at SEL access to table BTCOPTIONS
                Not authorized to object BTCOPTIONS in R3TSTDATA type *file
                Job=378721/TST02/WP02’
    Database error text........: "Not authorized to object SCPRACTR in R3TSTDATA  
    type *FILE. Job=379089/TST02/WP00"                                           
    I have also run GRTOBJAUT for the - TST02 user on the R3TSTDATA lib but still the same problem.
    I'm certain the issue is related to the user on the 400 that is actually used by the work processes, and that user does not have the relevant rights to R3TSTDATA.
    Any suggestions on how to resolve this problem will be humbly received.
    Many thanks, Colin

    Hi,
    step 9 is wrong ;-(((
    old:
    9. AS4FIXFILE on R3TSTDATA with
    DBLIB R3TSTDATA
    CHGOWN *NO
    ENDJRN *YES
    STRJRN *YES
    CHGFILE *NO
    correct:
    9. AS4FIXFILE on R3TSTDATA with
    DBLIB R3TSTDATA
    CHGOWN *YES    <<<<<
    ENDJRN *YES
    STRJRN *YES
    CHGFILE *NO
    it NEEDS to run with QSECOFR !!!
    => it will work !
    GRTOBJAUT on all objects is rubbish only !!! no real solution!!!
    Regards
    Volker Gueldenpfennig, consolut international ag
    http://www.consolut.de - http://www.4soi.de - http://www.easymarketplace.de

Maybe you are looking for

  • Error while copying from crm to R/3

    Hi, An error has occured while coping an installation order from crm to R/3. Any suggestions mates. Error message is:An error has occured in the system R3PCLNT501 while copying the document Regards, Jan.

  • How To Keep Your iPhone Safe At The Gym

    I have a problem with the Otterbox Defender (or more like a worry). Here is my  worry.  I like to use my iPhone at the gym.  I also have an iPod touch.   I have used the iPod touch at the gym, with no problems (it has a very  thin rubber protector).

  • External Hard Drive "partial" crash?

    Ive been using a 500 gb GDrive mini triple for about 6 months now to store all of my data for school and it has been great, until now. I dont kow exactly what happened, but now "most" of my files are corrupt (the important ones conveniently). I had p

  • StreamCorruptedException in ObjectInputStream

    Hello!! I have a problem with serialization and ObjectInputStream/ObjectOutputStream classes: I have two programs. The first program writes objects in a file. Here is the code: FileOutputStream f = new FileOutputStream ("filename", true); ObjectOutpu

  • Need to view BPM graphically in P7.1

    Hi All,           I have executed a simple BPM where the flow is good.When I click on PE hyperlink to view the flow in graphics,I get the following: Process Overview on Integration Server Only How do I view the BPM flow graphically. Regards, Premjit