MOS-01012 during Oracle Pre-Load phase system copy
Hello,
The problem is in phase 'Oracle Pre-Load Actions', we have error:
MOS-01012 PROBLEM: '/sapmnt/Q02/exe/saplicense -R3Setup Q02 "OMLRUURS" TRACE=2' returned with '254' which is not a defined as a success code.
Homogenous system copy, AIX, ORA 9.2.0.8
I've checked a few things:
- when I manually execute this command I have:
Fri Jan 28 17:04:02 2011
MtxInit: 0 0 0
- R3trans -d is ok (rc 0000)
- Q02 database is up
- oracle listener is up
- saplicense -show
LICENSE system: Q02 hardware key: N1153195602 expiration_date: 99991231
installation no: 0110004123 key: xxxxx
userlimit: 0 productid: R3_ORA
system-nr: 000000000310644498
license useable ***
- saplicense -get (returns N1153195602)
- saplicense.log contain:
Fri Jan 28 17:04:02 2011
MtxInit: 0 0 0
I'm stuck, no more idea...
Best regards,
MIchal
dev_slic contains:
SlicIGetDate: <20110129>
SlicPwForR3Setup: calc password out of <Q0220110129FJAWFNLTL>
SlicIGetDate: <20110129>
SlicSapInstall: sysname: >Q02< connect: >1< rollback: >1<
SlicIDbLock: first call to SlicIDbLock: initialize Mutex
db_con_init called
create_con (con_name=R/3)
Loading DB library '/sapmnt/Q02/exe/dboraslib.o' ...
load shared library (/sapmnt/Q02/exe/dboraslib.o), hdl 0
Library '/sapmnt/Q02/exe/dboraslib.o' loaded
function DbSlExpFuns loaded from library /sapmnt/Q02/exe/dboraslib.o
Version of '/sapmnt/Q02/exe/dboraslib.o' is "640.00", patchlevel (0.220)
function dsql_db_init loaded from library /sapmnt/Q02/exe/dboraslib.o
function dbdd_exp_funs loaded from library /sapmnt/Q02/exe/dboraslib.o
New connection 0 created
0: name = R/3, con_id = -000000001 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
db_con_connect (con_name=R/3)
find_con_by_name found the following connection for reuse:
0: name = R/3, con_id = 000000000 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
Got ORACLE_HOME=/oracle/Q02/920_64 from environment
-->oci_initialize (con_hdl=0)
got NLS_LANG='AMERICAN_AMERICA.UTF8' from environment
ERROR => OCI-call 'OCIEnvCreate(mode=16384)' failed: rc = -1 [dboci.c 2287]
set_ocica() -> OCI or SQL return code -1
ERROR => OCI-call 'OCIErrorGet' failed: rc = -2 [dboci.c 2081]
-->oci_initialize (con_hdl=0)
got NLS_LANG='AMERICAN_AMERICA.UTF8' from environment
Client NLS settings:
Logon as OPS$-user to get SAPQ02's password
Connecting as /@Q02 on connection 0 (nls_hdl 0) ... (dbsl 640 070308)
Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch
0 0 (nil) (nil) (nil)
Allocating service context handle for con_hdl=0
ERROR => OCI-call 'OCIHandleAlloc' failed: rc = -2 [dboci.c 2830]
ERROR => CONNECT failed with sql error '-2' [dbsloci.c 11395]
set_ocica() -> OCI or SQL return code -2
ERROR => OCI-call 'OCIErrorGet' failed: rc = -2 [dboci.c 2081]
Try to connect with default password
Connecting as SAPQ02/<pwd>@Q02 on connection 0 (nls_hdl 0) ... (dbsl 640 070308)
Nls CharacterSet NationalCharSet C EnvHp ErrHp ErrHpBatch
0 0 (nil) (nil) (nil)
Allocating service context handle for con_hdl=0
ERROR => OCI-call 'OCIHandleAlloc' failed: rc = -2 [dboci.c 2830]
ERROR => CONNECT failed with sql error '-2' [dbsloci.c 11395]
set_ocica() -> OCI or SQL return code -2
ERROR => OCI-call 'OCIErrorGet' failed: rc = -2 [dboci.c 2081]
Edited by: Michal Sarna on Jan 29, 2011 4:37 PM
> Got ORACLE_HOME=/oracle/Q02/920_64 from environment
> -->oci_initialize (con_hdl=0)
> got NLS_LANG='AMERICAN_AMERICA.UTF8' from environment
> *** ERROR => OCI-call 'OCIEnvCreate(mode=16384)' failed: rc = -1 [dboci.c 2287]
> set_ocica() -> OCI or SQL return code -1
> *** ERROR => OCI-call 'OCIErrorGet' failed: rc = -2 [dboci.c 2081]
> -->oci_initialize (con_hdl=0)
Did you install the Oracle 9.2.0.8 client? Or did you link the binaries from the ORACLE_HOME? Or are you using the Oracle client from the installation DVD?
Markus
Similar Messages
-
Problems with the Oracle Pre-Load actions in an homogeneous system copy
Hi,
I am trying to do a NW04 homogeneous system copy, and I am having troubles with the ABAP copy. (Oracle Pre-Load Actions step)
I am with the database specific procedure, so I am creating the new system until the sapinst asks me to bring an online-offline backup and the control file, then the sapinst tries to recover the database by himself, but he finds trouble:
Error: CJS-00084 SQL statement or script failed.<br>DIAGNOSIS: Error message: ORA-01194: file 1 needs more recovery to be consistent Ora-01110: data file 1: 'oracle/XIE...'
If I try to do the recover manually I have to make the usual:
RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE;
CANCEL
ALTER DATABASE OPEN RESETLOGS;
If I follow the sapinst.log I find that the sapinst tries to recover the database but fails with the above message and:
ORA-01589: must use RESETLOGS or NORESETLOGS option for database open
Yes, that's true, if I make it manually I have to open the database with the 'alter database open resetlogs';
the problem could be fixed modifying the run_control.sql statement that the SAPINST creates at the working directory, but no modification to that statement is possible because the SAPINST deletes and creates the statement IMMEDIATELY before executing it, so what can I do?
Many thanks
MarioSOLVED
for your info, the run_control.sql is UNMODIFIABLE, but I could modify the CONTROL.SQL that he calls, so I recovered manually the Database, and the CONTROL.SQL was a simply CONNECT and then OPEN DATABASE, just like that, so I could continue with my installation, another point for us against the damned SAPINST !!! -
HI All,
I am trying to install SAP R/3 4.7 IDES, Oracle 9 with patch 9.2.0.3.0 on 2003 Server SP2. I have encountered the following error during Database Instance installation step of Oracle Pre-load Actions .
CJS-00084 SQL Statement or Script failed. Error Message: Executable C:\oracle\ora92/bin/sqlplus.exe returns 3.
ERROR 2007-06-13 10:25:46
FJS-00012 Error when executing script.
I have already tried following solutions.
1) directory C:\oracle\ora92/bin/sqlplus.exe is there I able to connect as sysdba
2) I changed C:\SAPinst_Oracle_KERNEL" name with no spaces
3) Installed Oracle without installing Database.
I think I am making a mistake in following two steps.
1) I did installed Ms Loop Back adapter but what exact entry I need to put in Host file?
2) When I installed Oracle and run Sapserver.cmd file, windows message popup and ask which program I want to use to open Sapserver.rsp file and I choose notepad.
After Oracle installed, I run some Sqlplus commands and able to connect as sysdba but listener status command showing one listener is running and other status unknow. After installation stop, Listener status giving TNS adapter error.
Please help.>> have already tried following solutions.
>>1) directory C:\oracle\ora92/bin/sqlplus.exe is there I able to connect as sysdba
>>2) I changed C:\SAPinst_Oracle_KERNEL" name with no spaces
>>3) Installed Oracle without installing Database.
never change the directory name of SAPinst working directory. It is designed in this version to use a directory with spaces and it will work with it.
What you should not do is to copy additional CDs (like Export, Kernel) into directories having blanks in the path.
>>1) I did installed Ms Loop Back adapter but what exact entry I need to put in Host file?
>>2) When I installed Oracle and run Sapserver.cmd file, windows message popup and ask which program I want to use to open Sapserver.rsp file and I choose notepad.
That should not happen at all.
The response file is opened by Oracle's setup.exe which is invoked by sapserver.cmd. Is the Oracle CD located on a directory containing blanks?
Peter -
DB2 9.7 DFACT.SQL syntax error in Import ABAP phase - System Copy
Hi all. I'm trying a system copy with a source system SAP ECC 6.0 ehp4 based on NW 701 and db2 LUW 9.1 .
As it seems supported by SAP, i'm using db2 LUW 9.7 in target system.
O.S. is Windows 2008.
I got an error in phase "Import ABAP".
Sapinst.log says:
INFO 2010-02-18 10:12:14.337
An error occured and the user decided to retry the current step: "|NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor".
INFO 2010-02-18 10:12:14.509
Switched to user: devadm.
INFO 2010-02-18 10:12:14.572
Creating file C:\Program Files\sapinst_instdir\ERPEhP4\LM\COPY\DB6\SYSTEM\CENTRAL\AS-ABAP\import_monitor.java.log.
INFO 2010-02-18 10:12:14.603
Switched to user: devadm.
INFO 2010-02-18 10:12:14.618
Working directory changed to C:\Program Files\sapinst_instdir\ERPEhP4\LM\COPY\DB6\SYSTEM\CENTRAL\AS-ABAP.
INFO 2010-02-18 10:12:14.618
Output of C:\j2sdk1.4.2_24-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is written to the logfile import_monitor.java.log.
WARNING 2010-02-18 10:12:44.790
Execution of the command "C:\j2sdk1.4.2_24-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2_24-rev"
Java(TM) Platform, Standard Edition for Business (build 1.4.2_24-rev-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_24-rev-b06, mixed mode)
Import Monitor jobs: running 1, waiting 1, completed 73, failed 0, total 75.
Loading of 'SAPDFACT' import package: ERROR
Import Monitor jobs: running 0, waiting 1, completed 73, failed 1, total 75.
WARNING[E] 2010-02-18 10:12:44.790
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
ERROR 2010-02-18 10:12:44.790
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
Looking into import_monitor.java.log i found that the problem is in dfact import.
I've looked into sapdfact.log and i found:
S:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20100218105045
S:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#8 $ SAP
S:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: version R7.01/V1.4 [UNICODE]
Compiled Jan 28 2010 20:22:25
S:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe -i SAPDFACT.cmd -dbcodepage 4103 -l SAPDFACT.log -stop_on_error -loadprocedure fast LOAD:COMPRESS_ALL
(DB) INFO: connected to DB
(DB6) INFO: COMPRESS YES is set during table creation.
(DB6) DB2 9.5 automatic dictionary creation does not require an explicit REORG.
(DB6) Compression threshold is ignored.
(GSI) INFO: dbname = "DEV "
(GSI) INFO: vname = "DB6 "
(GSI) INFO: hostname = "UNKNOWN "
(GSI) INFO: sysname = "Windows NT"
(GSI) INFO: nodename = "SRVSAPDEV"
(GSI) INFO: release = "6.0"
(GSI) INFO: version = "6002 Service Pack 2"
(GSI) INFO: machine = "4x AMD64 Level 6 (Mod 26 Step 5)"
(DB) ERROR: DDL statement failed with SQL error
( ALTER TABLE "/BI0/E0PPM_VC1" DROP PRIMARY KEY )
(SQL error -539)
error message returned by dsql:
SQL0539N Table or nickname "SAPDEV./BI0/E0PPM_VC1" does not have a "PRIMARY" key. SQLSTATE=42888
(IMP) INFO: a failed DROP attempt is not necessarily a problem
(DB6) INFO: executing DDL statements for object /BI0/E0PPM_VC1 from external SQL file.
(DB) ERROR: DDL statement failed with SQL error
( CREATE TYPE 2 UNIQUE INDEX "/BI0/E0PPM_VC1~0" ON "/BI0/E0PPM_VC1" ("KEY_0PPM_VC1T" , "KEY_0PPM_VC11" , "KEY_0PPM_VC1U" , "KEY_0PPM_VC1P" ) USING STOGROUP ___FAI PRIQTY 16 SECQTY 10240 FREEPAGE 0 PCTFREE 0 GBPCACHE CHANGED DEFINE NO BUFFERPOOL BP3 COPY NO PIECESIZE 2097152 K CLUSTER NOT PADDED )
(SQL error -7)
error message returned by dsql:
SQL0007N The character "_" following "" ) USING STOGROUP" is not valid. SQLSTATE=42601
(DB) INFO: disconnected from DB
S:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
S:\usr\sap\DEV\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20100218105045
So as you can see it seems that there's some syntax error in dfacl.log. The wrong SQL statement referred by sapdfact.log is
ind: /BI0/E0PPM_VC1~0
sql: CREATE TYPE 2 UNIQUE INDEX "/BI0/E0PPM_VC1~0" ON "/BI0/E0PPM_VC1"
("KEY_0PPM_VC1T" ,
"KEY_0PPM_VC11" ,
"KEY_0PPM_VC1U" ,
"KEY_0PPM_VC1P" )
USING STOGROUP ___FAI PRIQTY 16
SECQTY 10240 FREEPAGE 0 PCTFREE 0
GBPCACHE CHANGED DEFINE NO
BUFFERPOOL BP3 COPY NO
PIECESIZE 2097152 K CLUSTER NOT PADDED ;
|
ALTER TABLE "/BI0/E0PPM_VC1"
ADD PRIMARY KEY ("KEY_0PPM_VC1T",
"KEY_0PPM_VC11",
"KEY_0PPM_VC1U",
"KEY_0PPM_VC1P") ;
Am i missing something?
Data in referred tables (infocubes) isn't really important.
Is there a safe way to proceed?
Thanks in advance.
Regards
Simone ZaffalonAnd this is the strange point: my source system is not a BI and my dataclasses .SQL files are not empty.
Me too i would expect that the files should be empty but instead they are full of object definitions.
For example i have APPL0.SQL that contains a list of all tables of ECC system, for example
tab: MAMT
sql: CREATE TABLE "MAMT"
("MANDT" SAPDB6VARCHAR(000003)
DEFAULT '000' NOT NULL,
"MATNR" SAPDB6VARCHAR(000018)
DEFAULT ' ' NOT NULL,
"SPRAS" SAPDB6VARCHAR(000001)
DEFAULT ' ' NOT NULL,
"MEINH" SAPDB6VARCHAR(000003)
DEFAULT ' ' NOT NULL,
"MTXID" SAPDB6VARCHAR(000002)
DEFAULT ' ' NOT NULL,
"LFDNR" SAPDB6VARCHAR(000002)
DEFAULT '00' NOT NULL,
"MAKTM" SAPDB6VARCHAR(000040)
DEFAULT ' ' NOT NULL)
IN "&location&"
INDEX IN "&locationI&"
LONG IN "&locationL&"
COMPRESS YES;
ALTER TABLE "MAMT" LOCKSIZE ROW;
and like this for all others tables.
What would occur if i launch an import with such .SQL files?
(shuld i put this question to another thread or is fine for you to answer on this?)
Thank you again.
Simone Zaffalon -
Oracle 8.1.7 system copy 6.20
Hello
I have a DEV machine installed 6.40, i deleted database files oracle 8.1.7 sap crm 3.0, then o copied from PRD the files again.
and the sid changes... how can i change it ?
Now i want to make a system copy. How can I do ?
I created manually the control.sql, where i Copy this file?
I have to use 6.20/6.40 master intalation? but there is not comming crm 3.0, just 4.0...for system copy...which one i should use?
any1 can tell me step by step, or using r3load, or something without using any instalation dvd ?
what i have to do for make it run again.
thanks
regards.
Pheno
SAP Jr.Adminsitratorthanks,
i need to ask some questions:
1- In system copy make differente if its CRM 3.0 or 4.0 or NW2004s or something?
like in master dvd 6.40 i dont find anything related of CRM3.0, just CRM 4.0.
2- what about database password? how can I reset it?
3- this documents its in Unix, the parameter are same for windows?
thank you very much for your help
Regards -
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,
MarianaDear 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 -
System copy for ECC 6.0 system no j2ee process under MMC
Dear support,
This has been observed in many of our clients system which are on ECC 6.0 abap+java system, that after we perform system copy from one system to another
whether it is Oracle platform or mssql server platform ( system copy for oracle using controlfile script ) ( system copy for mssql with restoring .BAK file from source )
systems are running fine but j2ee process table showing no processes like
SDM, dispatcher , server0
even configtool and go.bat are unable to connect.
Is there any specific settings we do after system copy for java side
Please let me know at earliest, as it is most strange thing i have seen in almost all my system where system copy is performed.I have already raised a post against this error but at that time i was not aware of this system copy reason behind the same.
Best regards,
AjitRYour main problem is not, that you don't see anything in MMC (the system can be added manually without much hazzle) - but is, that you database content of schema SAP<SID>DB does not match the data found on the filesystem.
If you copy the filesystem structure from production to test/qa, you need to make sure, the database and filesystem are in sync. You will have two problems if you "just copy them":
- They are out of sync because your production was going on running since you copied the backup files
- all configuration (all java property sheets) is/are set to point to the production system instead of the test/qa system
I doubt, that it will work if you copy it over. This also explains, why you can't even start configtool, because it points to the wrong system/schema. You MAY be able to fix all that manually, but you may encounter subsequent errors because not all configuration is documented, you would need to step into the whole j2ee tree and look at each and every propertysheet to find out, whether it's correct or not. Additionally, the database may have other information (see above) and all that may become overwritten during bootstrap.
So - the best way to get your system up and running quickly is to start sapinst on the source system, export your Java instance (not using ABAP but the Java dump) and re-importing that to your test/qa system.
Markus -
Installation Master DVD Distributed Java System Copy menu missing
Hello Gurus
We want to perfom an Java system copy of our EP 6.0 using sapinst
The source OS is Solaris 8.0 with Oracle 10.2.0.2
The target OS is Solaris 10.0 with Oracle 10.2.0.2
Our architecture is Distributed , CI is running on a system and DB server on another system.
For this operation we use the master DVD 51033746_12 but we have an issue in exporting the DB as the
Option for exporting the DB on a Distributed system is not displayed on the sapinst Menu .
We followed the last guide taken from sap 'Homogeneous and Heterogeneous System Copy for SAP Systems Based on SAP Web Application Server Java 6.40 SR 1' and this option should be listed
Excerpt:
Choose the installation service SAP NetWeaver u201904 Support Release 1--> Java System --><DB> --> Distributed System --> Migration - Database Export.
Unfortunately the Distributed system is not displayed and though we are stuck at the export step .
I could not find any sapinst patches . Is it a known issue for Soalris system and is there a Workaround .
Thanks for your help
De Palma Lionel .Hello
Thanks for your answer . Unfortunately this option is not available as we are using a NW04 SR1 system , not a nw'2004's one . With the latest master install (Installation_Master_6.20_6.40_05_08 51033746_5 )we have the choice of
System copy Source --> Java system --> oracle --> Migration Data export
--> HA Java system --> oracle --> Migration Data export
System copy Target --> Java system --> oracle --> Central system-> Migration Data export
Target --> Java system --> oracle --> Distributed system -> Migration Target Central instance / Db instance install
The Distributed system is available for Import option but no for the export one .
My questions are :
- Can we use a master nw2004's master DVD for system copy on a Nw'04s one ?
- As the central instance is hosted on different system than DB instance , should I use the HA option ?
Regards -
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 -
Unable to open the export file during Import ABAP phase on tar(System copy)
Hi Experts,
We are encountering the following error during Import ABAP phase on target system as we are performing system copy on target system as part of hardware migration(Data center migration).
Scenario:
Sourrce system - BI- ABAP(7.01), Win 2003 x64 unicode,Oracle 10.2.0.4
Target system - BI-ABAP(7.01), Win 2008 R2 unicode, Oracle 11.2.0.1
Actually on source system the data has been generated using migration monitor by using table splitting option and transferred on target system thru ftp option.
During Import process while selecting the Database installation type we have selected the installation method as "Standard systemcopy/Migration(load based)" and not checked the option "Start Migration montior Manually".
As far as my concern this error has nothing to do with this selection.please correct me If i am wrong.
T:\usr\sap\BWS\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20110428082000
T:\usr\sap\BWS\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/701_REL/src/R3ld/R3load/R3ldmain.c#5 $ SAP
T:\usr\sap\BWS\SYS\exe\uc\NTAMD64\R3load.exe: version R7.01/V1.4 [UNICODE]
Compiled Feb 24 2009 23:41:07
T:\usr\sap\BWS\SYS\exe\uc\NTAMD64\R3load.exe -dbcodepage 4103 -i test_MIGKEY.cmd -l test_MIGKEY.log -K
DbSl Trace: ORA-1403 when accessing table SAPUSER
(DB) INFO: connected to DB
(DB) INFO: DbSlControl(DBSL_CMD_NLS_CHARACTERSET_GET): UTF8
(TFH) ERROR: Unable to open
10.207.3.59\d$\ftproot\import_sap\BWS\ABAP\DATA\ARFCSDATA.TOC
(TFH) ERROR: OS error message: Invalid argument
T:\usr\sap\BWS\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
T:\usr\sap\BWS\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20110428082003
Kindly revert with resolutions and suggestions and any hint to the oss notes as we haven't found anything specific to this error.
Regrds,
Dheeraj\\10.207.3.59\d$\ftproot\import_sap\BWS\ABAP\DATA\ARFCSDATA.TOC
Please check if above said file located under specified path where SAPINST searvhing for it ie at
10.207.3.59\d$\ftproot\import_sap\BWS\ABAP\DATA. if this file dont exist them it may be the case that your export is not proper.
Also check if user from which you have started this SAPINST is able to access
10.207.3.59\d$\ftproot\import_sap\BWS\ABAP\DATA.
Thanks..
Mohit -
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 PMDear 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 -
Error during Heterogeneous System Copy - Phase 18 Import ABAP
Hello gurus,
I´m facing an error during the Target Installation in a Heterogeneous System Copy (Migration). The system SAP is a SAP ECC 6.0 SR3 (Unicode and Abap+Java).
Source server:
Operation System: Windows 2003 Server x64
Database: SQL Server 2008 SP01
Target server:
Operation System: Red Hat Enterprise Linux (RHEL) X64
Database: Oracle DB 10.2g (10.2.0.4)
I already did the all procedures in export database and all that looks fine!
At this point I´m running the system copy procedure through SAPInst on target server (RHEL / Oracle) but in phase 18 - Import ABAP the sapinst stops... (by the way in procedure bar, I can see "Import Monitor jobs: running 0, waiting 1, completed 0, failed 18, total 19")
I checked three log files (sapinst_dev.log ; sapinst.log ; SAPSDIC.log):
SAPSDIC.log:
/usr/sap/QAS/SYS/exe/run/R3load: START OF LOG: 20100820145140
/usr/sap/QAS/SYS/exe/run/R3load: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#14 $ SAP
/usr/sap/QAS/SYS/exe/run/R3load: version R7.00/V1.4 [UNICODE]
Compiled Jan 23 2008 17:39:05
/usr/sap/QAS/SYS/exe/run/R3load -ctf I /software/export_preparation/ABAP/DATA/SAPSDIC.STR /tmp/sapinst_instdir/NW04S/LM/COPY/ORA/SYSTEM/CENTRAL/AS/DDLORA.TPL SAPSDIC.TSK ORA -l SAPSDIC.log
(TPL) ERROR: unknown template variable "compress"
/usr/sap/QAS/SYS/exe/run/R3load: job finished with 1 error(s)
/usr/sap/QAS/SYS/exe/run/R3load: END OF LOG: 20100820145140Hi Volker,
> (TPL) ERROR: unknown template variable "compress"
> This message looks like the DDLORA.TPL contains stuff that should not belong there.
> Can you attach the DDLORA.TPL.
> There are some bugs with SMIGR_CREATE_DDL, but they are mostly not related to oracle.
prikey: AFTER_LOAD ORDER_BY_PKEY
seckey: AFTER_LOAD
cretab: CREATE TABLE &tab_name&
( /{ &fld_name& &fld_desc& /-, /} )
TABLESPACE &tablespace&
&compress&
&lob_cache&
STORAGE (INITIAL &init&
NEXT &next&
MINEXTENTS &minext&
MAXEXTENTS &maxext&
PCTINCREASE &pctinc& )
drptab: DROP TABLE &tab_name&
crepky: CREATE UNIQUE INDEX &pri_key&
ON &tab_name&
( &key_fld& /-, )
TABLESPACE &tablespace&
STORAGE (INITIAL &init&
NEXT &next&
MINEXTENTS &minext&
MAXEXTENTS &maxext&
PCTINCREASE &pctinc& )
NOLOGGING
COMPUTE STATISTICS ;
ALTER INDEX &pri_key& LOGGING
drppky: DROP INDEX &pri_key&
creind: CREATE &unique& INDEX &ind_name&
ON &tab_name&
( /{ &fld_name& /-, /} )
TABLESPACE &tablespace&
STORAGE (INITIAL &init&
NEXT &next&
MINEXTENTS &minext&
MAXEXTENTS &maxext&
PCTINCREASE &pctinc& )
NOLOGGING
COMPUTE STATISTICS ;
ALTER INDEX &ind_name& LOGGING
drpind: DROP INDEX &ind_name&
crevie: CREATE VIEW &view_name&
( /{ &fld_name& /-, /} )
AS &query&
drpvie: DROP VIEW &view_name&
trcdat: TRUNCATE TABLE &tab_name&
deldat: DELETE FROM &tab_name& &where&
negtab: LICHECK MLICHECK
negdat: LICHECK MLICHECK
negind: LICHECK0 MLICHECK0 LICHECK0 MLICHECK0
negvie:
negcpr:ARFCSSTATE ARFCSDATA ARFCRSTATE TRFCQDATA TRFCQIN TRFCQOUT TRFCQSTATE QRFCTRACE QRFCLOG
table storage parameters
loc: APPL0 PSAPSR3 0000
APPL1 PSAPSR3 0000
APPL2 PSAPSR3 0000
CLUST PSAPSR3 0000
DDIM PSAPSR3 0000
DFACT PSAPSR3 0000
DODS PSAPSR3 0000
POOL PSAPSR3 0000
SDIC PSAPSR3 0
SDOCU PSAPSR3 0000
SLDEF PSAPSR3700 0000
SLEXC PSAPSR3700 0000
SLOAD PSAPSR3 0000
SPROT PSAPSR3 0000
SSDEF PSAPSR3700 0000
SSEXC PSAPSR3700 0000
SSRC PSAPSR3 0000
TEMP PSAPSR3 0000
USER PSAPSR3USR 0000
USER1 PSAPSR3USR 0000
sto: 0 0000000016K 0000000040K 0000000001 2147483645
1 0000000016K 0000000160K 0000000001 2147483645
10 0000000016K 0000655360K 0000000001 2147483645
11 0000000016K 0001310720K 0000000001 2147483645
12 0000000016K 0002621440K 0000000001 2147483645
13 0000000016K 0005242880K 0000000001 2147483645
14 0000000016K 0010485760K 0000000001 2147483645
2 0000000016K 0000000640K 0000000001 2147483645
3 0000000016K 0000002560K 0000000001 2147483645
4 0000000016K 0000010240K 0000000001 2147483645
5 0000000016K 0000020480K 0000000001 2147483645
6 0000000016K 0000040960K 0000000001 2147483645
7 0000000016K 0000081920K 0000000001 2147483645
8 0000000016K 0000163840K 0000000001 2147483645
9 0000000016K 0000327680K 0000000001 2147483645
index storage parameters
loc: APPL0 PSAPSR3 0000
APPL1 PSAPSR3 0000
APPL2 PSAPSR3 0000
CLUST PSAPSR3 0000
DDIM PSAPSR3 0000
DFACT PSAPSR3 0000
DODS PSAPSR3 0000
POOL PSAPSR3 0000
SDIC PSAPSR3 0
SDOCU PSAPSR3 0000
SLDEF PSAPSR3700 0000
SLEXC PSAPSR3700 0000
SLOAD PSAPSR3 0000
SPROT PSAPSR3 0000
SSDEF PSAPSR3700 0000
SSEXC PSAPSR3700 0000
SSRC PSAPSR3 0000
TEMP PSAPSR3 0000
USER PSAPSR3USR 0000
USER1 PSAPSR3USR 0000
sto: 0 0000000016K 0000000040K 0000000001 2147483645
1 0000000016K 0000000080K 0000000001 2147483645
10 0000000016K 0000163840K 0000000001 2147483645
11 0000000016K 0000327680K 0000000001 2147483645
12 0000000016K 0000655360K 0000000001 2147483645
13 0000000016K 0001310720K 0000000001 2147483645
14 0000000016K 0002621440K 0000000001 2147483645
2 0000000016K 0000000160K 0000000001 2147483645
3 0000000016K 0000000640K 0000000001 2147483645
4 0000000016K 0000002560K 0000000001 2147483645
5 0000000016K 0000005120K 0000000001 2147483645
6 0000000016K 0000010240K 0000000001 2147483645
7 0000000016K 0000020480K 0000000001 2147483645
8 0000000016K 0000040960K 0000000001 2147483645
9 0000000016K 0000081920K 0000000001 2147483645 -
Why NetWeaver04 DB instance takes more time during 'Database Load' phase?
Hi,
I'm installing NetWeaver04 CI and DB instances on Solaris 10 machine and as a standalone installation. CI was installed fine and DB instance install takes forever and i don't know how long it will take because i started this at 17.20 and now it is 22.01. Here is the summary of my install.
1. Installed CI
Note: Unicode ABAP install
2. Ran DB instance install:
Note:Selected Advanced database options instead of RAW device
3. Completed Oracle install and continued for DB instance install
Note: Selected Unicode option and selected Enterprise install
4. The install so far completed 25 out of 39 tasks and it is waiting for more than 4 hrs at Database Load phase.
I'm not sure what will be the result of my install. I would like to know whether it is supposed to take that long for DB instance install. Could someone tell me what would be the reason and what would i've missed in the install steps.
Thanks,
RamThe load is by far the most time consuming operation; you can make this run faster if you have a large amount of hardware by increasing the number of parallel R3trans jobs (default is 3) during the installation. It's not uncommon for this step to run for several hours if you don't increase this parameter.
Also, you might watch the oracle alert log; if your archive directory fills up, the load will just hang indefinitly. If you create your oraarch filesystem with at least 4 GB of space, this shouldn't be an issue during the initial load, but if it's much smaller, you could run into a problem there....
Rich -
Pre-loading the Cache from Database during application start-up
We are using Spring, Hibernate, Oracle Coherence 3.5.2 Weblogic Webservices
Our requirement is to pre-load the cache during the application start-up most probably during Authentication/Authorization Service is invoked.
We plan to load the data for other services from database into Coherence cache so that whenever user access that particular service he ends up hitting the Cache instead of database.
We would greatly appreciate sample code snippets on how to write CacheInitializerBean with marker to demonstrate the state of cache.Hi Rob,
Thanks for pointing to the article: Pre-Loading the Cache
In fact i already looked at that article before posting. It just mentions how to load the data from database into Cache.
What i am looking for is how to make this happen during application start-up. This is my first hurdle.
The second one is as mentioned in the article http://coherence.oracle.com/display/COH35UG/Pre-Loading+the+Cache
i wrote following code which never gets populated into cache. Not sure whats going wrong even though i see Hibernate loadAll() method loading all the objects in the console
public void populateCache() throws SQLException
Map<Long, Object> buffer = new HashMap<Long, Object>();
int count = 0;
List<Contract> contractList = this.getHibernateTemplate().loadAll(Contract.class);
log.debug("contractList size="+contractList.size());
for(Contract contract : contractList)
Long key = new Long(contract.getId());
Object value = contract;
buffer.put(key, value);
// this loads 1000 items at a time into the cache
if ((count++ % 1000) == 0)
contractCache.putAll(buffer);
buffer.clear();
if (!buffer.isEmpty())
contractCache.putAll(buffer);
}We would greatly appreciate your time in helping us resolving two hurdle blocks. -
Pre-loading Oracle text in memory with Oracle 12c
There is a white paper from Roger Ford that explains how to load the Oracle index in memory : http://www.oracle.com/technetwork/database/enterprise-edition/mem-load-082296.html
In our application, Oracle 12c, we are indexing a big XML field (which is stored as XMLType with storage secure file) with the PATH_SECTION_GROUP. If I don't load the I table (DR$..$I) into memory using the technique explained in the white paper then I cannot have decent performance (and especially not predictable performance, it looks like if the blocks from the TOKEN_INFO columns are not memory then performance can fall sharply)
But after migrating to oracle 12c, I got a different problem, which I can reproduce: when I create the index it is relatively small (as seen with ctx_report.index_size) and by applying the technique from the whitepaper, I can pin the DR$ I table into memory. But as soon as I do a ctx_ddl.optimize_index('Index','REBUILD') the size becomes much bigger and I can't pin the index in memory. Not sure if it is bug or not.
What I found as work-around is to build the index with the following storage options:
ctx_ddl.create_preference('TEST_STO','BASIC_STORAGE');
ctx_ddl.set_attribute ('TEST_STO', 'BIG_IO', 'YES' );
ctx_ddl.set_attribute ('TEST_STO', 'SEPARATE_OFFSETS', 'NO' );
so that the token_info column will be stored in a secure file. Then I can change the storage of that column to put it in the keep buffer cache, and write a procedure to read the LOB so that it will be loaded in the keep cache. The size of the LOB column is more or less the same as when creating the index without the BIG_IO option but it remains constant even after a ctx_dll.optimize_index. The procedure to read the LOB and to load it into the cache is very similar to the loaddollarR procedure from the white paper.
Because of the SDATA section, there is a new DR table (S table) and an IOT on top of it. This is not documented in the white paper (the white paper was written for Oracle 10g). In my case this DR$ S table is much used, and the IOT also, but putting it in the keep cache is not as important as the token_info column of the DR I table. A final note: doing SEPARATE_OFFSETS = 'YES' was very bad in my case, the combined size of the two columns is much bigger than having only the TOKEN_INFO column and both columns are read.
Here is an example on how to reproduce the problem with the size increasing when doing ctx_optimize
1. create the table
drop table test;
CREATE TABLE test
(ID NUMBER(9,0) NOT NULL ENABLE,
XML_DATA XMLTYPE
XMLTYPE COLUMN XML_DATA STORE AS SECUREFILE BINARY XML (tablespace users disable storage in row);
2. insert a few records
insert into test values(1,'<Book><TITLE>Tale of Two Cities</TITLE>It was the best of times.<Author NAME="Charles Dickens"> Born in England in the town, Stratford_Upon_Avon </Author></Book>');
insert into test values(2,'<BOOK><TITLE>The House of Mirth</TITLE>Written in 1905<Author NAME="Edith Wharton"> Wharton was born to George Frederic Jones and Lucretia Stevens Rhinelander in New York City.</Author></BOOK>');
insert into test values(3,'<BOOK><TITLE>Age of innocence</TITLE>She got a prize for it.<Author NAME="Edith Wharton"> Wharton was born to George Frederic Jones and Lucretia Stevens Rhinelander in New York City.</Author></BOOK>');
3. create the text index
drop index i_test;
exec ctx_ddl.create_section_group('TEST_SGP','PATH_SECTION_GROUP');
begin
CTX_DDL.ADD_SDATA_SECTION(group_name => 'TEST_SGP',
section_name => 'SData_02',
tag => 'SData_02',
datatype => 'varchar2');
end;
exec ctx_ddl.create_preference('TEST_STO','BASIC_STORAGE');
exec ctx_ddl.set_attribute('TEST_STO','I_TABLE_CLAUSE','tablespace USERS storage (initial 64K)');
exec ctx_ddl.set_attribute('TEST_STO','I_INDEX_CLAUSE','tablespace USERS storage (initial 64K) compress 2');
exec ctx_ddl.set_attribute ('TEST_STO', 'BIG_IO', 'NO' );
exec ctx_ddl.set_attribute ('TEST_STO', 'SEPARATE_OFFSETS', 'NO' );
create index I_TEST
on TEST (XML_DATA)
indextype is ctxsys.context
parameters('
section group "TEST_SGP"
storage "TEST_STO"
') parallel 2;
4. check the index size
select ctx_report.index_size('I_TEST') from dual;
it says :
TOTALS FOR INDEX TEST.I_TEST
TOTAL BLOCKS ALLOCATED: 104
TOTAL BLOCKS USED: 72
TOTAL BYTES ALLOCATED: 851,968 (832.00 KB)
TOTAL BYTES USED: 589,824 (576.00 KB)
4. optimize the index
exec ctx_ddl.optimize_index('I_TEST','REBUILD');
and now recompute the size, it says
TOTALS FOR INDEX TEST.I_TEST
TOTAL BLOCKS ALLOCATED: 1112
TOTAL BLOCKS USED: 1080
TOTAL BYTES ALLOCATED: 9,109,504 (8.69 MB)
TOTAL BYTES USED: 8,847,360 (8.44 MB)
which shows that it went from 576KB to 8.44MB. With a big index the difference is not so big, but still from 14G to 19G.
5. Workaround: use the BIG_IO option, so that the token_info column of the DR$ I table will be stored in a secure file and the size will stay relatively small. Then you can load this column in the cache using a procedure similar to
alter table DR$I_TEST$I storage (buffer_pool keep);
alter table dr$i_test$i modify lob(token_info) (cache storage (buffer_pool keep));
rem: now we must read the lob so that it will be loaded in the keep buffer pool, use the prccedure below
create or replace procedure loadTokenInfo is
type c_type is ref cursor;
c2 c_type;
s varchar2(2000);
b blob;
buff varchar2(100);
siz number;
off number;
cntr number;
begin
s := 'select token_info from DR$i_test$I';
open c2 for s;
loop
fetch c2 into b;
exit when c2%notfound;
siz := 10;
off := 1;
cntr := 0;
if dbms_lob.getlength(b) > 0 then
begin
loop
dbms_lob.read(b, siz, off, buff);
cntr := cntr + 1;
off := off + 4096;
end loop;
exception when no_data_found then
if cntr > 0 then
dbms_output.put_line('4K chunks fetched: '||cntr);
end if;
end;
end if;
end loop;
end;
Rgds, PierreI have been working a lot on that issue recently, I can give some more info.
First I totally agree with you, I don't like to use the keep_pool and I would love to avoid it. On the other hand, we have a specific use case : 90% of the activity in the DB is done by queuing and dbms_scheduler jobs where response time does not matter. All those processes are probably filling the buffer cache. We have a customer facing application that uses the text index to search the database : performance is critical for them.
What kind of performance do you have with your application ?
In my case, I have learned the hard way that having the index in memory (the DR$I table in fact) is the key : if it is not, then performance is poor. I find it reasonable to pin the DR$I table in memory and if you look at competitors this is what they do. With MongoDB they explicitly says that the index must be in memory. With elasticsearch, they use JVM's that are also in memory. And effectively, if you look at the awr report, you will see that Oracle is continuously accessing the DR$I table, there is a SQL similar to
SELECT /*+ DYNAMIC_SAMPLING(0) INDEX(i) */
TOKEN_FIRST, TOKEN_LAST, TOKEN_COUNT, ROWID
FROM DR$idxname$I
WHERE TOKEN_TEXT = :word AND TOKEN_TYPE = :wtype
ORDER BY TOKEN_TEXT, TOKEN_TYPE, TOKEN_FIRST
which is continuously done.
I think that the algorithm used by Oracle to keep blocks in cache is too complex. A just realized that in 12.1.0.2 (was released last week) there is finally a "killer" functionality, the in-memory parameters, with which you can pin tables or columns in memory with compression, etc. this looks ideal for the text index, I hope that R. Ford will finally update his white paper :-)
But my other problem was that the optimize_index in REBUILD mode caused the DR$I table to double in size : it seems crazy that this was closed as not a bug but it was and I can't do anything about it. It is a bug in my opinion, because the create index command and "alter index rebuild" command both result in a much smaller index, so why would the guys that developped the optimize function (is it another team, using another algorithm ?) make the index two times bigger ?
And for that the track I have been following is to put the index in a 16K tablespace : in this case the space used by the index remains more or less flat (increases but much more reasonably). The difficulty here is to pin the index in memory because the trick of R. Ford was not working anymore.
What worked:
first set the keep_pool to zero and set the db_16k_cache_size to instead. Then change the storage preference to make sure that everything you want to cache (mostly the DR$I) table come in the tablespace with the non-standard block size of 16k.
Then comes the tricky part : the pre-loading of the data in the buffer cache. The problem is that with Oracle 12c, Oracle will use direct_path_read for FTS which basically means that it bypasses the cache and read directory from file to the PGA !!! There is an event to avoid that, I was lucky to find it on a blog (I can't remember which, sorry for the credit).
I ended-up doing that. the events to 10949 is to avoid the direct path reads issue.
alter session set events '10949 trace name context forever, level 1';
alter table DR#idxname0001$I cache;
alter table DR#idxname0002$I cache;
alter table DR#idxname0003$I cache;
SELECT /*+ FULL(ITAB) CACHE(ITAB) */ SUM(TOKEN_COUNT), SUM(LENGTH(TOKEN_INFO)) FROM DR#idxname0001$I;
SELECT /*+ FULL(ITAB) CACHE(ITAB) */ SUM(TOKEN_COUNT), SUM(LENGTH(TOKEN_INFO)) FROM DR#idxname0002$I;
SELECT /*+ FULL(ITAB) CACHE(ITAB) */ SUM(TOKEN_COUNT), SUM(LENGTH(TOKEN_INFO)) FROM DR#idxname0003$I;
SELECT /*+ INDEX(ITAB) CACHE(ITAB) */ SUM(LENGTH(TOKEN_TEXT)) FROM DR#idxname0001$I ITAB;
SELECT /*+ INDEX(ITAB) CACHE(ITAB) */ SUM(LENGTH(TOKEN_TEXT)) FROM DR#idxname0002$I ITAB;
SELECT /*+ INDEX(ITAB) CACHE(ITAB) */ SUM(LENGTH(TOKEN_TEXT)) FROM DR#idxname0003$I ITAB;
It worked. With a big relief I expected to take some time out, but there was a last surprise. The command
exec ctx_ddl.optimize_index(idx_name=>'idxname',part_name=>'partname',optlevel=>'REBUILD');
gqve the following
ERROR at line 1:
ORA-20000: Oracle Text error:
DRG-50857: oracle error in drftoptrebxch
ORA-14097: column type or size mismatch in ALTER TABLE EXCHANGE PARTITION
ORA-06512: at "CTXSYS.DRUE", line 160
ORA-06512: at "CTXSYS.CTX_DDL", line 1141
ORA-06512: at line 1
Which is very much exactly described in a metalink note 1645634.1 but in the case of a non-partitioned index. The work-around given seemed very logical but it did not work in the case of a partitioned index. After experimenting, I found out that the bug occurs when the partitioned index is created with dbms_pclxutil.build_part_index procedure (this enables enables intra-partition parallelism in the index creation process). This is a very annoying and stupid bug, maybe there is a work-around, but did not find it on metalink
Other points of attention with the text index creation (stuff that surprised me at first !) ;
- if you use the dbms_pclxutil package, then the ctx_output logging does not work, because the index is created immediately and then populated in the background via dbms_jobs.
- this in combination with the fact that if you are on a RAC, you won't see any activity on the box can be very frightening : this is because oracle can choose to start the workers on the other node.
I understand much better how the text indexing works, I think it is a great technology which can scale via partitioning. But like always the design of the application is crucial, most of our problems come from the fact that we did not choose the right sectioning (we choosed PATH_SECTION_GROUP while XML_SECTION_GROUP is so much better IMO). Maybe later I can convince the dev to change the sectionining, especially because SDATA and MDATA section are not supported with PATCH_SECTION_GROUP (although it seems to work, even though we had one occurence of a bad result linked to the existence of SDATA in the index definition). Also the whole problematic of mixed structured/unstructured searches is completly tackled if one use XML_SECTION_GROUP with MDATA/SDATA (but of course the app was written for Oracle 10...)
Regards, Pierre
Maybe you are looking for
-
Time machine Deleted old computer backups
Hey, I have been using a mac pro for about a year and a half now and as all computers get it has become slow and full of garbage. So i used my time machine back up and successfully backed up all my files. I put in the OS disk and wiped the computer c
-
Display PDF and get possibly modified data back
Hello we want to display a PDF in the SAP-GUI, either inline or external via the registered application (Adobe Reader, Adobe Acrobat or whatever). If the user has an application that is capable of editing a PDF-Document, we need to get the document's
-
Loading multiple images dynamically
hi, trying to load several images to timeline keyframes, managed to load one, how to load several, Here´s the code: var imageLoader:Loader; function loadImage(url:String):void { imageLoader = new Loader(); imageLoader.load(new URLRequest(url)); image
-
I try to use FF for everything but this is the one thing I can't get it to do and I hate to have IE as my only choice for viewing these files correctly. They are for school, but I would still like to use them for websites I design.
-
"cor" file for problem analysis
Hello, I have 2 "sections" in "diagnosis files" that appeared after a database check, one on 29th 01 and the other yesterday. What can i do with these files ? ****For the "first" core file, i have done 2 checks : First : 2009-01-29 18:02:18 10874 ERR