System-copy failed
hi gurus,
I'm trying to make a system copy from WIN2000/ORA817 to WIN2003/ORA10g FOR R/3 4.6C SR2.
During the system-copy, I change the SCHEMA-ID from SR3 to DEV, and now it's in new tablespace layout, which means there're no PSAPDDICD/PSAPDDICI any longer.
I choose DBMIG.R3s to import Data, the db-loading has been finished, but the migration stopped during phase DBR3LICENSECREATE_NT_ORA, below are the dbmig.log
also I cannot use br*tools to show my tablespace due to invalid SAP License.
It's so werid, and I tried the Note 134592 - Importing the SAPDBA role ( sapdba_role.sql), but it doesn't work.
PS: when I do the system-copy for 46c SR2, can I change the db-schema ID or I have to retain it as SR3 for 46c, and change the SAP-SCHEMA ID to DEV?
Thank you all in advance if you can help on this.
Rgds, Sam
======DBMIG.LOG===========
INFO 2006-10-24 19:56:51
Creating the SAP System License
INFO 2006-10-24 19:56:51 DBR3LICENSECREATE_NT_ORA InternalInstallationDo:0
Create SAP license table.
ERROR 2006-10-24 19:56:51 DBR3LICENSECREATE_NT_ORA InternalInstallationDo:0
See logfile dev_slic for further information.
INFO 2006-10-24 19:56:51 DBR3LICENSECREATE_NT_ORA InternalInstallationDo:0
See logfile dev_slic for further information.
ERROR 2006-10-24 19:56:51 DBR3LICENSECREATE_NT_ORA InstallationDo:0
Phase failed.
ERROR 2006-10-24 19:56:51 InstController Action:0
Step DBR3LICENSECREATE_NT_ORA could not be performed.
ERROR 2006-10-24 19:56:51 Main
Installation failed.
ERROR 2006-10-24 19:56:51 Main
Installation aborted.
trc file: "dev_slic", trc level: 2, release: "46D"
[Thr 3780] Tue Oct 24 13:46:10 2006
[Thr 3780] SlicSapInstall: sysname: >DEV< connect: >1< rollback: >1<
[Thr 3780] Got TNS_ADMIN=
cnsh10sdev\SAPMNT\DEV\sys\profile\oracle from environment
[Thr 3780] Got ORACLE_SID=DEV from environment
[Thr 3780] Got NLS_LANG=AMERICAN_AMERICA.WE8DEC from environment
[Thr 3780] Logon as OPS$-user to get SAPDEV's password
[Thr 3780] Connecting as /@DEV on connection 0 ...
[Thr 3780] -->oci_logon(con_hdl=0, user='', dbname='DEV')
[Thr 3780] Now I'm connected to ORACLE using OCI_7 API
[Thr 3780] *** ERROR => ORA-1403 when accessing table SAPUSER [dbsloci.c 7803]
[Thr 3780] Disconnecting from connection 0 ...
[Thr 3780] -->oci_logoff(con_hdl=0)
[Thr 3780] Now I'm disconnected from ORACLE
[Thr 3780] Try to connect with default password
[Thr 3780] Connecting as SAPDEV/<pwd>@DEV on connection 0 ...
[Thr 3780] -->oci_logon(con_hdl=0, user='SAPDEV', dbname='DEV')
[Thr 3780] Now I'm connected to ORACLE using OCI_7 API
[Thr 3780] Database instance dev is running on CNSH10SDEV with ORACLE version 10.2.0.2.0 since 20061023
[Thr 3780] License index MLICHECK0 not found( - ok)
[Thr 3780] License index MLICHECK__0 not found( - ok)
[Thr 3780] License index MLICHECK~I1 not found( - ok)
[Thr 3780] Old license index not dropped...(rc: -111)
[Thr 3780] Database vendor is ORACLE
[Thr 3780] *** ERROR => ORA-959 occurred; SQL statement is ==> [dbsloci.c 5821]
[Thr 3780] CREATE TABLE MLICHECK (SYSTEMNAME varchar2(3) NOT NULL, CUSTOMERKEY varchar2(11) NOT NULL,\
[Thr 3780] PRODUCTID varchar2(20) NOT NULL, CUSTOMERINST varchar2(10) NOT NULL, USERLIMIT numbe\
[Thr 3780] r(10) NOT NULL, CREATION_DATE varchar2(8) NOT NULL, EXPIRATION_DATE varchar2(8) NOT NULL, LCHE\
[Thr 3780] CK_DATE varchar2(8) NOT NULL, LKEY varchar2(24) NOT NULL, FPRINT varchar2(2\
[Thr 3780] 4) NOT NULL) STORAGE(initial 16K next 16K pctincrease 0) tablespace PSAPDDICD ;
[Thr 3780] *** ERROR => DBSL statement where error happend:
CREATE TABLE MLICHECK (SYSTEMNAME varchar2(3) NOT NULL, CUSTOMERKEY varchar2(11) NOT NULL, PRODUCTID varchar2(20) NOT NULL, CUSTOMERINST varchar2(10) NOT NULL, USERLIMIT number(10) NOT NULL, CREATION_DATE varchar2(8) NOT NULL, EXPIRATION_DATE varchar2(8) NOT NULL, LCHECK_DATE varchar2(8) NOT NULL, LKEY varchar2(24) NOT NULL, FPRINT varchar2(24) NOT NULL) STORAGE(initial 16K next 16K pctincrease 0) tablespace PSAPDDICD [dbsloci.c 2220]
[Thr 3780]
[Thr 3780] * LOCATION CPIC (TCP/IP) on local host
[Thr 3780] * ERROR Creation of license table failed
[Thr 3780] *
TIME Tue Oct 24 13:46:10 2006
[Thr 3780] * RELEASE 46D
[Thr 3780] * COMPONENT SLIC
[Thr 3780] * VERSION 221
[Thr 3780] * RC 99
[Thr 3780] * MODULE slicdb.c
[Thr 3780] * LINE 879
[Thr 3780] * DETAIL DbSlExecute failed with return code 99
ORA-00959: tablespace 'PSAPDDICD' does not exist
[Thr 3780] * COUNTER 1
[Thr 3780] *
[Thr 3780] *****************************************************************************
[Thr 3780] *** ERROR => Failed to create license table (rc: -2) [slicfkt.c 342]
[Thr 3780] *** ERROR => Failed to create license table (rc: -2) [slicinst.c 218]
[Thr 3780] *** ERROR => SlicISapInstall: failed, rc -2 [slicinst.c 128]
[Thr 3780] Disconnecting from connection 0 ...
[Thr 3780] -->oci_logoff(con_hdl=0)
[Thr 3780] Now I'm disconnected from ORACLE
Hello Savo,
I finally make it by using the correct kernel disc which supports oracle 10g. I remove all the history work and did it again, and finally it's done.
During the new installation of CI and DBMIG, I chose the type 'New Tablespace Layout', and choose new database name and SAP System Name, but leaves the DBSCHEMA as SAPSR3,which is default.
Tks for you guys' valuable reply.
Rgds, Sam
Similar Messages
-
MAXDB Dataabase system Copy - Fail on Phase ABAP Import - Index
Hi All
I wonder if somebody can shed some light on the below; we are doing a system copy of Production BW to QA BW; on ABAP import phase we get an error in the log SAPAPPL1.log (The Database being used is MAXDB)
ERROR : Execute for create index /BI0/E0FC_C06P on /BI0/E0FC_C06 failed (dbrc=99). (SQL error -7055) error message returned by DbSl: SQL-Statement: CREATE INDEX "/BI0/E0FC_C06P" ON "/BI0/E0FC_C06" ( "KEY_0FC_C06P" , "KEY_0FC_C06T" , "KEY_0FC_C06U" , "KEY_0FC_C061" , "KEY_0FC_C062" , "KEY_0FC_C063" , "KEY_0FC_C064" , "KEY_0FC_C065" )
I have checked in the releavant TSK file to see whether I can change the offending line from "err" to "ok", this does not help;
Second thing I tried to do was to drop the index using but keep on getting message that index does not exist
Any help would be apreciated, would I need to re-run the export
Kind Regards
Peter> I wonder if somebody can shed some light on the below; we are doing a system copy of Production BW to QA BW; on ABAP import phase we get an error in the log SAPAPPL1.log (The Database being used is MAXDB)
>
> ERROR : Execute for create index /BI0/E0FC_C06P on /BI0/E0FC_C06 failed (dbrc=99). (SQL error -7055) error message returned by DbSl: SQL-Statement: CREATE INDEX "/BI0/E0FC_C06P" ON "/BI0/E0FC_C06" ( "KEY_0FC_C06P" , "KEY_0FC_C06T" , "KEY_0FC_C06U" , "KEY_0FC_C061" , "KEY_0FC_C062" , "KEY_0FC_C063" , "KEY_0FC_C064" , "KEY_0FC_C065" )
>
> I have checked in the releavant TSK file to see whether I can change the offending line from "err" to "ok", this does not help;
Did you execute the report SMIGR_CREATE_DDL on the source system and placed the resulting .SQL files in the ABAP/DB/ADA directory before starting the import?
Markus -
BDLS Conversion after System Copy fails
Hi All,
We are doing a Homogeneous System Copy on a AIX 5.3/Oracle 10.2.0.4/ SAP ERP 6.0 environment.
After the system copy we had to run BDLS to convert logical system names in tables. Except for 3 tables namely EDPP1, TBD05 and TBD06 the BDLS run was successful.
We tried to convert the logical system names in these tables by running BDLS for these tables individually however they failed again.
The error was - "Error in field of table. Manual correction required"
I checked SAP Note 121163 and it is mentioned in this note -
"If the new logical system name already exists in the system, it can cause errors for tables in which the logical system is key field or
unique index (for example, COFIO1). In this case the number of converted entries is smaller than the number of selected entries."
And in this case a manual post-processing is required. How do I go about doing this manual post-processing?
1. Should I maintain these directly at the table level - which is cumbersome as there are a lot of entries?
2. Or using a small ABAP program?
Please let me know if any other information is required frommy side.
Thanks, DibyaHi,
Yes ofcourse, you need to check all settinfs, once you copy teh system you are going loose all RFC's and Source and Destinations ectc, so adject all that settings.
See the following SAP Notes:
SAP Note 886102 - System Landscape Copy for SAP NetWeaver BW
SAP Note 325470 - Activities after client copy in BW source systems
SAP Note 325525 - Copying and renaming systems in a BW environment
SAP Note 1333302 - Special procedure for BW system copy
SAP Note 996238 - Dump 'RFC connection error' after BW system copy
Search for PDF in SDN
How Tou2026System Copy in SAP Business Intelligence System Landscapes
Thanks
Reddy -
Export for system copy fails - Error 9 (Bad file number)
Hello all,
I am attempting to perform the export phase for a hetergenous system copy on our BI system (BI 7.0 - NW2004s). This system runs on HP-UX 11.11 using Oracle 10.2.0.2 and will be migrated to Windows Server 2003 and MS SQL Server 2005, once the export is complete.
While running sapinst to export the data from the source system, there are several input dialog screens that are skipped, which means I am not able to enter all the paramters used for the export. After seeing this behavior from sapinst, I reviewed the sapinst.log and sapinst_dev.log files and find the warning/error "System call failed. Error 9 (Bad file number)". I have included a portion of these files below.
I have reviewed notes 546006 and 583861, but these seem to refer to an Oracle error ORA-27121, but I am not receiving any Oracle errors in sapinst.log or the Oracle alert log. I have looked for possible permission or ownership problems with any of the SAP or Oracle files, but have not found any that were incorrect. Also, these errors do not specify which file sapinst is having problems with, so I do not have a specific file or area to check.
If anyone has seen something similar to this and has any suggestions, I would greatly appreciate any help.
sapinst.log details:
INFO 2009-02-14 15:15:51.67
Execute step collect of component |NW_Export|ind|ind|ind|ind|0|0|NW_GetSidFromProfiles|ind|ind|ind|ind|1|0|NW_readProfileDir|ind|ind
|ind|ind|0|0
INFO 2009-02-14 15:15:52.737
Account bwpadm already exists.
WARNING 2009-02-14 15:15:52.747
System call failed. Error 9 (Bad file number) in execution of system call 'getgrent' with parameter (), line (292) in file (syuxcuse
r.cpp).
INFO 2009-02-14 15:15:52.757
Account 0 already exists.
WARNING 2009-02-14 15:15:52.777
System call failed. Error 9 (Bad file number) in execution of system call 'getgrent' with parameter (), line (292) in file (syuxcuse
r.cpp).
INFO 2009-02-14 15:15:52.777
Account 200 already exists.
WARNING 2009-02-14 15:15:52.827
System call failed. Error 9 (Bad file number) in execution of system call 'getgrent' with parameter (), line (292) in file (syuxcuse
r.cpp).
INFO 2009-02-14 15:16:04.937
Creating file /tmp/sapinst_instdir/NW04S/LM/COPY/ORA/EXP/CENTRAL/AS/EXP/ypcat.log.
INFO 2009-02-14 15:16:05.007
Output of ypcat passwd.byname is written to the logfile ypcat.log.
sapinst_dev.log details:
TRACE 2009-02-14 15:15:52.737
2009-02-14 15:15:52.743 NW._getSAPMount() done: /sapmnt
INFO 2009-02-14 15:15:52.737 [syuxcaccmg.cpp:227]
bool CSyAccountMgtImpl::isExisting(ISyAccountMgt::eAccountType accountType, iastring sName)
Account bwpadm already exists.
TRACE 2009-02-14 15:15:52.747 [syuxcuser.cpp:1943]
CSyUserImpl_getOsInfos(ILogBook *m_logBook, iastring sName, iastring sID, tSyUserInfo& msUserinfo)
getspnam(bwpadm) returned NULL.
WARNING 2009-02-14 15:15:52.747 [syxxsyshlp.cpp:78]
syslib::printOSError(const iastring &, int, DWORD, const iastring &, CMessage::eLogMessage)
System call failed. Error 9 (Bad file number) in execution of system call 'getgrent' with parameter (), line (292) in file (syuxcuse
r.cpp).
Regards,
Rusty RobbinsHello Peter,
Thanks for the reply. I did confirm the points you made, and have the details below.
1. check filesystem, if you have enough space, especially /tmp
All filesystems have available space, and /tmp has 310 MB available, before the start of sapinst.
2. check again alert log, trace log for Oracle,
I could not find any errors in the alert_SID.log or any unusual trace files.
3. How did you run sapinst? Are you using "root" account.
I am running sapinst as user root and I am following all the recomendations in the system copy guide (at least as far as I can tell. ;p )
We have four BI systems in this landscape, and the other three have migrated successfully. The procedure I am using, is the same as for the other 3 systems and uses the same SAP media directory that was used on the other systems.
One other item that may be part of my problem here, is that this system is the production system, and was originally installed as a high-availability system, using HP-UX Service Guard for clustering. Currently, this system does not have fail-over enabled, but of course the cluster is still intact. One required piece of the Service Guard enviornment is the use of a virtual hostname. This seems to resolve successfully by sapinst, as I see the correct (virtual) hostname referenced several times. While this is a clustered system (for fail-over purposes), the CI and DB are installed on the same host. So it is not a distributed system, and if failover had been initiated, it would fail both the CI and DB instance, which is the same and only SAP instance.
This did raise one question in my mind, however. I am attempting to extract this using the following menu path within sapinst.
SAP NetWeaver 7.0 Support Release 3 --> Software Life-Cycle Options --> System Copy --> Oracle --> Source System Export --> Central System --> Based on AS ABAP and AS Java
Since this does use Service Guard, but is not a distributed system, should I be using a different path in the sapinst tree, for the export? I have only performed a migration using the above path, so I am not familar with the detailf of the other types, such as High-Availabitly or Distributed-System.
Regards,
Rusty -
Homogeneous System Copy failing on Phase Running J2EE Migration
Hi All,
I am running a Homogeneous System Copy according to the System Copy manual. (SAPinst not SV/RST) It is failing on Phase Running J2EE Migration which tells me to look at my RUNJMT.log (below), but it doesn't seem to give me much direction. As anyone run into this before?:
An error occurred while processing service SAP NetWeaver 7.0 Support Release 3 > Software Life-Cycle Options > System Copy > IBM DB2 for i5/OS > Target System Installation > Central System > Based on AS ABAP and AS Java > Central System( Last error reported by the step :Error when running the Java Migration Toolkit. SOLUTION: See output of logfile Y:\usr\sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS//runJmt.log: ' com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: cluster_data/server, at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.readConfig(PersistenceHandler.java:108) at com.sap.engine.core.configuration.impl.cache.CachedConfiguration. (CachedConfiguration.java:62) at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:848) at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:882) at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.openConfiguration(ConfigurationCache.java:748) at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:734) at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:693) at com.sap.sdt.serviceframework630.impl.ClusterDataImpl._getSourceIds0(ClusterDataImpl.java:54) at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.getServerIds(ClusterDataImpl.java:108) at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.createIdMapping(ClusterDataImpl.java:174) at com.sap.sdt.jmt.migrationtool.MigrationToolImport.prepareSwitch(MigrationToolImport.java:1129) at com.sap.sdt.jmt.migrationtool.MigrationToolImport.startTool(MigrationToolImport.java:403) at com.sap.sdt.jmt.migrationtool.MigrationToolImport.main(MigrationToolImport.java:1561) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60) at java.lang.reflect.Method.invoke(Method.java:391) at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)'.). You may now
choose Retry to repeat the current step.
choose View Log to get more information about the error.
stop the task and continue with it later.
Log files are written to Y:\usr\sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/.
runjmt.log:
com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: cluster_data/server,
at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.readConfig(PersistenceHandler.java:108)
at com.sap.engine.core.configuration.impl.cache.CachedConfiguration.<init>(CachedConfiguration.java:62)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:848)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:882)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.openConfiguration(ConfigurationCache.java:748)
at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:734)
at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:693)
at com.sap.sdt.serviceframework630.impl.ClusterDataImpl._getSourceIds0(ClusterDataImpl.java:54)
at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.getServerIds(ClusterDataImpl.java:108)
at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.createIdMapping(ClusterDataImpl.java:174)
at com.sap.sdt.jmt.migrationtool.MigrationToolImport.prepareSwitch(MigrationToolImport.java:1129)
at com.sap.sdt.jmt.migrationtool.MigrationToolImport.startTool(MigrationToolImport.java:403)
at com.sap.sdt.jmt.migrationtool.MigrationToolImport.main(MigrationToolImport.java:1561)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)Here is version '9' fo the SAPinst.log
INFO 2010-06-15 09:20:24.952
Creating file Y:\usr\sap\SAPinst\NW04S\LM\COPY\DB4\SYSTEM\CENTRAL\AS\x.
INFO 2010-06-15 09:20:24.952
Removing file Y:\usr\sap\SAPinst\NW04S\LM\COPY\DB4\SYSTEM\CENTRAL\AS\x.
INFO 2010-06-15 09:21:12.656
Creating file C:\Program Files (x86)\SAPinst\x.
INFO 2010-06-15 09:21:12.656
Removing file C:\Program Files (x86)\SAPinst\x.
INFO 2010-06-15 09:21:28.313
Copied file 'Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/statistic.xml' to 'Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/statistic.24.xml'.
INFO 2010-06-15 09:21:39.798
Copied file 'Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/statistic.xml' to 'Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/statistic.25.xml'.
WARNING 2010-06-15 09:22:11.095
Unable to get information about path
LABEL.ASC\ using GetVolumeInformation. Operating system error message: The filename, directory name, or volume label syntax is incorrect.
INFO 2010-06-15 09:22:18.595
Copied file 'Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/inifile.xml' to 'Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/inifile.9.xml'.
INFO 2010-06-15 09:22:23.798
Copied file 'Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/keydb.xml' to 'Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/keydb.9.xml'.
INFO 2010-06-15 09:22:38.814
Copied file 'Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/statistic.xml' to 'Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/statistic.26.xml'.
INFO 2010-06-15 09:22:45.908
Execute step RunMigrationController of component |NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|4|0|NW_RUN_MIGRATION_CONTROLLER|ind|ind|ind|ind|2|0
INFO 2010-06-15 09:23:25.675
Creating file Y:\usr\sap\SAPinst\NW04S\LM\COPY\DB4\SYSTEM\CENTRAL\AS\runJmt.log.
INFO 2010-06-15 09:23:32.175
Working directory changed to Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/jmt.
INFO 2010-06-15 09:23:39.800
Working directory changed to Y:\usr\sap\SAPinst\NW04S\LM\COPY\DB4\SYSTEM\CENTRAL\AS.
INFO 2010-06-15 09:23:39.956
Removed environment variable JANITOR_400 from current process environment.
INFO 2010-06-15 09:23:44.878
Output of \qopensys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath /usr/sap/BID/SYS/global/sltools/sharedlib/launcher.jar;. com.sap.engine.offline.OfflineToolStart com.sap.sdt.jmt.migrationtool.MigrationToolImport /usr/sap/BID/SYS/global/sltools/jmt:/usr/sap/BID/SYS/global/sltools/sharedlib import.switch resume downtime mti.properties is written to the logfile Y:/usr/sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS/runJmt.log.
WARNING 2010-06-15 09:23:45.456
Execution of the command "\qopensys\QIBM\ProdData\JavaVM\jdk14\64bit\bin\java -classpath /usr/sap/BID/SYS/global/sltools/sharedlib/launcher.jar;. com.sap.engine.offline.OfflineToolStart com.sap.sdt.jmt.migrationtool.MigrationToolImport /usr/sap/BID/SYS/global/sltools/jmt:/usr/sap/BID/SYS/global/sltools/sharedlib import.switch resume downtime mti.properties" finished with return code 2. Output:
com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: cluster_data/server,
at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.readConfig(PersistenceHandler.java:108)
at com.sap.engine.core.configuration.impl.cache.CachedConfiguration.<init>(CachedConfiguration.java:62)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:848)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:882)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.openConfiguration(ConfigurationCache.java:748)
at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:734)
at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:693)
at com.sap.sdt.serviceframework630.impl.ClusterDataImpl._getSourceIds0(ClusterDataImpl.java:54)
at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.getServerIds(ClusterDataImpl.java:108)
at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.createIdMapping(ClusterDataImpl.java:174)
at com.sap.sdt.jmt.migrationtool.MigrationToolImport.prepareSwitch(MigrationToolImport.java:1129)
at com.sap.sdt.jmt.migrationtool.MigrationToolImport.startTool(MigrationToolImport.java:403)
at com.sap.sdt.jmt.migrationtool.MigrationToolImport.main(MigrationToolImport.java:1561)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
ERROR 2010-06-15 09:23:45.534
CJS-20068 Error when running the Java Migration Toolkit. SOLUTION: See output of logfile Y:\usr\sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS//runJmt.log: '
com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: cluster_data/server,
at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.readConfig(PersistenceHandler.java:108)
at com.sap.engine.core.configuration.impl.cache.CachedConfiguration.<init>(CachedConfiguration.java:62)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:848)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:882)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.openConfiguration(ConfigurationCache.java:748)
at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:734)
at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:693)
at com.sap.sdt.serviceframework630.impl.ClusterDataImpl._getSourceIds0(ClusterDataImpl.java:54)
at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.getServerIds(ClusterDataImpl.java:108)
at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.createIdMapping(ClusterDataImpl.java:174)
at com.sap.sdt.jmt.migrationtool.MigrationToolImport.prepareSwitch(MigrationToolImport.java:1129)
at com.sap.sdt.jmt.migrationtool.MigrationToolImport.startTool(MigrationToolImport.java:403)
at com.sap.sdt.jmt.migrationtool.MigrationToolImport.main(MigrationToolImport.java:1561)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)'.
ERROR 2010-06-15 09:23:45.534
CJS-20068 Error when running the Java Migration Toolkit. SOLUTION: See output of logfile Y:\usr\sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS//runJmt.log: '
com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: cluster_data/server,
at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.readConfig(PersistenceHandler.java:108)
at com.sap.engine.core.configuration.impl.cache.CachedConfiguration.<init>(CachedConfiguration.java:62)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:848)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:882)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.openConfiguration(ConfigurationCache.java:748)
at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:734)
at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:693)
at com.sap.sdt.serviceframework630.impl.ClusterDataImpl._getSourceIds0(ClusterDataImpl.java:54)
at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.getServerIds(ClusterDataImpl.java:108)
at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.createIdMapping(ClusterDataImpl.java:174)
at com.sap.sdt.jmt.migrationtool.MigrationToolImport.prepareSwitch(MigrationToolImport.java:1129)
at com.sap.sdt.jmt.migrationtool.MigrationToolImport.startTool(MigrationToolImport.java:403)
at com.sap.sdt.jmt.migrationtool.MigrationToolImport.main(MigrationToolImport.java:1561)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)'.
ERROR 2010-06-15 09:23:46.644
FCO-00011 The step RunMigrationController with step key |NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|4|0|NW_RUN_MIGRATION_CONTROLLER|ind|ind|ind|ind|2|0|RunMigrationController was executed with status ERROR ( Last error reported by the step :Error when running the Java Migration Toolkit. SOLUTION: See output of logfile Y:\usr\sap/SAPinst/NW04S/LM/COPY/DB4/SYSTEM/CENTRAL/AS//runJmt.log: '
com.sap.engine.frame.core.configuration.ConfigurationException: Error occurred during DB access: cluster_data/server,
at com.sap.engine.core.configuration.impl.persistence.rdbms.PersistenceHandler.readConfig(PersistenceHandler.java:108)
at com.sap.engine.core.configuration.impl.cache.CachedConfiguration.<init>(CachedConfiguration.java:62)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:848)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.getCachedConfiguration(ConfigurationCache.java:882)
at com.sap.engine.core.configuration.impl.cache.ConfigurationCache.openConfiguration(ConfigurationCache.java:748)
at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:734)
at com.sap.engine.core.configuration.impl.ConfigurationHandlerImpl.openConfiguration(ConfigurationHandlerImpl.java:693)
at com.sap.sdt.serviceframework630.impl.ClusterDataImpl._getSourceIds0(ClusterDataImpl.java:54)
at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.getServerIds(ClusterDataImpl.java:108)
at com.sap.sdt.serviceframework630.impl.ClusterDataImpl.createIdMapping(ClusterDataImpl.java:174)
at com.sap.sdt.jmt.migrationtool.MigrationToolImport.prepareSwitch(MigrationToolImport.java:1129)
at com.sap.sdt.jmt.migrationtool.MigrationToolImport.startTool(MigrationToolImport.java:403)
at com.sap.sdt.jmt.migrationtool.MigrationToolImport.main(MigrationToolImport.java:1561)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:88)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:61)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)'.).
INFO 2010-06-15 09:26:38.491
An error occured and the user decide to stop.\n Current step "|NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CI_Instance|ind|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|ind|ind|ind|ind|4|0|NW_RUN_MIGRATION_CONTROLLER|ind|ind|ind|ind|2|0|RunMigrationController".
INFO 2010-06-15 09:29:23.322
Creating file C:\Program Files (x86)\SAPinst\.lastInstallationLocation.
INFO 2010-06-15 09:29:29.510
Creating file Y:\usr\sap\SAPinst\NW04S\LM\COPY\DB4\SYSTEM\CENTRAL\AS\__instana_tmp.xml. -
Mixed (Java & ABAP w/different sources) System Copy Failed- NW 7.0 SR3/SP14
Hello SAP Friends! Our NW admin did a dual stack system copy where the ABAP server came from system 1 and the Java server came from system 2. This worked fine for ABAP (duh it was installed first), but the Java system copy was a disaster. the server started but many key services did not.
Why?
Many of the configuration entries were not generated properly. For example, a new, unknown SID was created, and many entries referenced System 1 (the ABAP source, not even the Java source). We were able to find and fix some incorrect config entries, but we still couldn't get all of the services we needed to work.
I think NW is so complicated that such a configuration is probably impossible, but maybe I am wrong.
Does anyone have tips? Or can confirm that this would never work?
The current plan is to install the Java Server from scratch as an add-in, which is less effort than searching through all the config files without any certainty that it will work. Hopefully it will work.
Many thanks in advance.Hi Matt,
What kind of infos are you looking for? I didn't perform the copy, have just been trying to figure out how to get all of the Java stack's services to start properly. As far as I know, it was done using the standard System Copy wizard. The ABAP server was done as a central instance and then the Java server was copied and installed as a java add-in.
I have asked the admin to post the details to this thread, but it would be helpful if you could mention what types of info and details you are looking for.
Thanks and Best Regards,
John -
DB Error during System Copy Import
Hello,
We are currently doing a heterogeneous system copy of an internal Solution Manager
7.01 (running on Linux SLES10 SP2 64Bit) to a new machine (running on
Linux SLES11 SP1 64Bit). The database we are using on both side is MaxDB.
During the export phase, nothing went wrong. The pre and post requisites were implemented.
But during the import phase with sapinst and more especially during the 'import ABAP' step we are facing the following errors.
__SAPDFACT.log :__
(IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
rc = 26, table "/BI0/F0SMD_PI2H"
DbSl Trace: EXECUTE on connection 0, rc=-7055 (POS(59) Column(s) already
indexed:/BI0/E0CCMARCDH~P)
ERROR : Execute for create index /BI0/E0CCMARCDH~P on /BI0/E0CCMARCDH
failed (dbrc=99).
(SQL error -7055)
error message returned by DbSl:
SQL-Statement: CREATE INDEX "/BI0/E0CCMARCDH~P" ON "/BI0/E0CCMARCDH" (
"KEY_0CCMARCDHP" , "KEY_0CCMARCDHT" , "KEY_0CCMARCDHU" ,
"KEY_0CCMARCDH1" , "KEY_0CCMARCDH2" , "KEY_0CCMARCDH3" ,
"KEY_0CCMARCDH4" , "KEY_0CCMARCDH5" , "KEY_0CCMARCDH6" ,
"KEY_0CCMARCDH7" , "KEY_0CCMARCDH8" , "KEY_0CCMARCDH9" ,
"KEY_0CCMARCDHB" )
SAPAPPL1.log :
(DB) ERROR: DDL statement failed
(DROP INDEX "/TMWFLOW/TRORDHT~1" ON "/TMWFLOW/TRORDHT")
DbSlExecute: rc = 103
(SQL error -4011)
error message returned by DbSl:
(IMP) INFO: a failed DROP attempt is not necessarily a problem
DbSl Trace: EXECUTE on connection 0, rc=-7055 (POS(59) Column(s) already
indexed:/BI0/E0CCMARCDH~P)
ERROR : Execute for create index /BI0/E0CCMARCDH~P on /BI0/E0CCMARCDH
failed (dbrc=99).
(SQL error -7055)
error message returned by DbSl:
SQL-Statement: CREATE INDEX "/BI0/E0CCMARCDH~P" ON "/BI0/E0CCMARCDH" (
"KEY_0CCMARCDHP" , "KEY_0CCMARCDHT" , "KEY_0CCMARCDHU" ,
"KEY_0CCMARCDH1" , "KEY_0CCMARCDH2" , "KEY_0CCMARCDH3" ,
"KEY_0CCMARCDH4" , "KEY_0CCMARCDH5" , "KEY_0CCMARCDH6" ,
"KEY_0CCMARCDH7" , "KEY_0CCMARCDH8" , "KEY_0CCMARCDH9" ,
"KEY_0CCMARCDHB" )
Before the export we executed the report for the DDL migration, created
the right *.sql files. We copied those sql files in the right folder
according to note 771209 and the System Copy guide.
We also tried to implement note 942540 - System copy fails on SAPDFACT
import, but we are not able to drop the mentioned tables. We are
getting 'unknown tables' whereas we see them in DB.
We would like to avoid restarting the export and import phases from the beggining as there is approximately 80GB to transfer each time and we are not running this on a server but desktop PC.
Any help would be appreciated.
Thanks in advance
Regards,
JohannHello Andreas
thank you for your answer. However, the table specified in the Note is not found when I am running the specified request in the correct schema:
-4004: POS(16) Unknown table name:/MAXDB/INDEXSTATEMENTS SQLSTATE: 42000
SAP_BW component in Solution Manager 7.01 SPS24 is SAPKW70106. As this BW release is already more recent than the one recommended in the Note, this issue should not be link to an old BW component patch version then.
In the meantime, I have applied Notes 888210 and 942540. But I cannot drop the tables specified since the user SAPSMJ has no DROPIN privilege and I cannot grant them even when using SUPERDBA user.
So I think we need to re-run the export as we are running out of options to try continuing the import phase.
Regarding the use of last R3load release, would you know the path to download it on the marketplace and if I need the last R3load kernel version (7.3) or only the last patch for 7.01 and knowing that I am using Netweaver 7.01 packages for the copy ? R3load used so far is 7.01/V1.4.
Thanks and Regards,
Johann -
SWPM - System Copy - Assertion Failed Unable to load database
Hello again,
(already the next question form me, sorry for this
I am executing a sysetm copy (DB-refresh) on ASE using SWPM.
However, in "Configure Components" step I get the error: Assertion failed. Unable to load database <SID of Target Sysetm>.
Where else can I check for errors?
I think it is still something on which I already worked (with other thread).
In sapinst_dev.log I found this
TRACE 2015-03-25 11:05:00.320
SAPInst calls the LogInquirer. The output of the LogInquirer can be found in file sapinst_loginquirer.log.
TRACE 2015-03-25 11:05:06.122 [iaxxgenimp.cpp:638]
CGuiEngineImp::showMessageBox()
<html> <head> </head> <body> <p> An error occurred while processing option <i>SAP Enhancement Package 1 for SAP N
etWeaver 7.3 > SAP ASE > System Copy > Target System > Standard System > Based on AS ABAP > Database Refresh or M
ove( Last error reported by the step: Assertion failed: Unable to load database <SID>.)</i>. You can now: </p> <ul>
<li> Choose <i>Retry</i><br>to repeat the current step. </li> <li> Choose <i>Log Files</i><br>to get more inform
ation about the error. </li> <li> Stop the option and continue later. </li> </ul> <p> Log files are written to /t
mp/sapinst_instdir/NW731/SYB/COPY/SYSTEM/STD/AS-ABAP/REF. </p> </body></html>
TRACE 2015-03-25 11:05:06.124 [iaxxgenimp.cpp:1031]
CGuiEngineImp::acceptAnswerForBlockingRequest
Waiting for an answer from GUI
In sapinst.log I found this:
ERROR 2015-03-25 11:04:59.573
FCO-00011 The step syb_step_setup_preload with step key |NW_ABAP_DB_DBRefresh|ind|ind|ind|ind|0|0|NW_ABAP_DB|ind
|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_CreateDB|ind|ind|ind|ind|createdb|0|NW_S
YB_DB|ind|ind|ind|ind|SYB_DB_CONTEXT|0|syb_step_setup_preload was executed with status ERROR ( Last error reporte
d by the step: Assertion failed: Unable to load database <SID>.).
INFO 2015-03-25 11:04:59.772
Creating file /tmp/sapinst_instdir/NW731/SYB/COPY/SYSTEM/STD/AS-ABAP/REF/__instana_tmp.xml.
INFO 2015-03-25 11:05:00.307
Removed file /tmp/sapinst_instdir/NW731/SYB/COPY/SYSTEM/STD/AS-ABAP/REF/instslana.xml.
INFO 2015-03-25 11:05:00.308
Creating file /tmp/sapinst_instdir/NW731/SYB/COPY/SYSTEM/STD/AS-ABAP/REF/instslana.xml.Hello Kiran,
I did a few tests again yesterday, and it was really a stupid mistake from myside.
The error message did mean, that there wasn't enough space.
It isn't the authority issue, it was a leak of space.
FYI, the complete DB-Size of Source System is required - NOT JUST RESERVED SPACE!!!
Thx for help and sorry for stealing your time :O -
System copy using SAPInst(Export Import database Independent prcoess failed
Hello ,
I am doing a System copy using SAPInst export/import process .
Source system : SAP Netweaver'04( BW 3.5 , Kernel : UC 640 ,Patch level 196 )
Export process fails at Phase 2 - Database Export at R3load jobs running 1,waiting 0 . Below is the log details
SAPSDIC.log
(EXP) INFO: entry for BAPICONTEN in DDNTT is newer than in DDNTT_CONV_UC: 20040211101817 > 20000621155733
(EXP) INFO: entry for BAPICONTENT255 in DDNTT is newer than in DDNTT_CONV_UC: 20040211101817 > 20031127161249
(EXP) INFO: entry for BAPICONVRS in DDNTT is newer than in DDNTT_CONV_UC: 20040211101817 > 20010131174038
(EXP) INFO: entry for BAPICREATORDATA in DDNTT is newer than in DDNTT_CONV_UC: 20040211101817 > 20000621155733
(EXP) INFO: entry for BAPICRMDH1 in DDNTT is newer than in DDNTT_CONV_UC: 20051229175654 > 20031211120714
(EXP) INFO: entry for BAPICRMDH2 in DDNTT is newer than in DDNTT_CONV_UC: 20051229175654 > 20031211120714
(EXP) INFO: entry for BAPICRMEXP in DDNTT is newer than in DDNTT_CONV_UC: 20051229175513 > 20031211120627
(EXP) INFO: entry for BAPICRMEXT in DDNTT is newer than in DDNTT_CONV_UC: 20051229175514 > 20031211120627
(EXP) INFO: entry for BAPICRMKEY in DDNTT is newer than in DDNTT_CONV_UC: 20051229175654 > 20031211120714
(EXP) INFO: entry for BAPICRMKEY_T in DDNTT is newer than in DDNTT_CONV_UC: 20051229175835 > 20031211120803
(EXP) INFO: entry for BAPICRMMSG in DDNTT is newer than in DDNTT_CONV_UC: 20051229175654 > 20031211120714
(EXP) INFO: entry for BAPICRMMSG_T in DDNTT is newer than in DDNTT_CONV_UC: 20051229175835 > 20031211120803
(EXP) INFO: entry for BAPICRMOBJ in DDNTT is newer than in DDNTT_CONV_UC: 20051229175514 > 20031211120628
(EXP) INFO: entry for BAPICRMPAREX_T in DDNTT is newer than in DDNTT_CONV_UC: 20051229175452 > 20031211120305
(EXP) INFO: limit reached, 5000 tables in DDNTT are newer than in DDNTT_CONV_UC
(EXP) INFO: NameTab check finished. Result=2 #20100113131216
(EXP) INFO: check for inactive NameTab entries: Ok.
(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
(DB) INFO: disconnected from DB
D:\usr\sap\B35\SYS\exe\run/R3load.exe: job finished with 1 error(s)
D:\usr\sap\B35\SYS\exe\run/R3load.exe: END OF LOG: 20100113131216
***SAPCLUST.log ****
(NT) Warn: EDIDOC: normal NameTab from 20040211095029 younger than alternate NameTab from 20000621155733!
(EXP) TABLE: "EDIDOC"
(NT) Warn: PCDCLS: normal NameTab from 20040211095029 younger than alternate NameTab from 20000621155733!
(EXP) TABLE: "PCDCLS"
(NT) Warn: SFHOA: normal NameTab from 20040211095029 younger than alternate NameTab from 20000621155733!
(EXP) TABLE: "SFHOA"
(NT) Warn: SFHYT: normal NameTab from 20040211095029 younger than alternate NameTab from 20000621155733!
(EXP) TABLE: "SFHYT"
(NT) Warn: UMG_TEST_C: normal NameTab from 20040211095029 younger than alternate NameTab from 20031113150115!
(EXP) TABLE: "UMG_TEST_C"
myCluster (55.22.Exp): 712: error when retrieving alternate nametab description for physical table UMG_TEST_F.
myCluster (55.22.Exp): 713: return code received from nametab is 32
myCluster (55.22.Exp): 299: error when retrieving physical nametab for table UMG_TEST_F.
(CNV) ERROR: data conversion failed. rc = 2
(RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
(DB) INFO: disconnected from DB
D:\usr\sap\B35\SYS\exe\run/R3load.exe: job finished with 1 error(s)
D:\usr\sap\B35\SYS\exe\run/R3load.exe: END OF LOG: 2010011312563
Please suggest.
Thanks & Regards
GaneshIs your DB unicode? If so, did you select the unicode flag in sapinst?
This [thread|System Copy Error while exporting ABAP; might offer some help.
-Zach -
How to reprocess failed monitor jobs in Import ABAP phase of system copy
Hi Experts,
Can you please let me know how to reprocess the failed monitor jobs during Import ABAP phase as i am performing the import of data as part of system copy of ABAP stack.
But i have not got any errors so far as the import process is running fine but there are few jobs which are showing as failed.Hence how can i reprocess these failed jobs again.
Regards,
DheerajHi Juan,
Here you go.And i have not selected the option" Start migration monitor manually "and where as on Source system the guy has used migration monitor option in order to split the tables and ftp for transferring the export data on target system.
Is this error anything to do with that?
Import Monitor.java.log
Import Monitor jobs: running 1, waiting 1, completed 223, failed 13, total 238.
Loading of 'RSERRORHEAD' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 224, failed 13, total 238.
Import.monitor.log
WARNING: 2011-04-30 02:57:31
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2011-04-30 02:57:31
13 error(s) during processing of packages.
INFO: 2011-04-30 02:57:31
Import Monitor is stopped.
SAPINST_dev.log
TRACE 2011-04-30 02:57:37.578 [iaxxgenimp.cpp:699]
CGuiEngineImp::showMessageBox
<html> <head> </head> <body> <p> An error occurred while processing option <i>SAP NetWeaver 7.0 including Enhancement Package 1 Support Release 1 > Software Life-Cycle Options > System Copy > Oracle > Target System Installation > Central System > Based on AS ABAP > Central System( Last error reported by the step: Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.)</i>. You can now: </p> <ul> <li> Choose <i>Retry</i> to repeat the current step. </li> <li> Choose <i>Log Files</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 <code>C:\Program Files/sapinst_instdir/NW701/LM/COPY/ORA/SYSTEM/CENTRAL/AS-ABAP/</code>. </p> </body></html>
TRACE 2011-04-30 02:57:37.578 [iaxxgenimp.cpp:1248]
CGuiEngineImp::acceptAnswerForBlockingRequest
Waiting for an answer from GUI
Regards,
Dheeraj -
BRCONNECT fails after system copy
Hi
After doing a system copy , in transaction DB13 , all my jobs are failing with "insufficient privileges" . I have already applied the following note
113747 , 583861 and 717677.
Please help..............
Job started
Step 001 started (program RSDBAJOB, variant &0000000000595, user ID BASIS)
Execute logical command BRCONNECT On host r3qa
Parameters: -u / -c -f check
BR0801I BRCONNECT 6.40 (38)
BR0280I BRCONNECT time stamp: 2006-11-30 19.42.35
BR0301W SQL error -1031 at location BrDbaSynCheck-9
ORA-01031: insufficient privileges
BR0602E No valid SAP license found - please contact SAP
BR0280I BRCONNECT time stamp: 2006-11-30 19.42.47
BR0301W SQL error -942 at location brc_dblog_open-1
ORA-00942: table or view does not exist
BR0324W Insertion of database log header failed
BR0806I End of BRCONNECT processing: cdubdqwp.log2006-11-30 19.42.47
BR0280I BRCONNECT time stamp: 2006-11-30 19.42.47
BR0804I BRCONNECT terminated with errors
External program terminated with exit code 3
BRCONNECT returned error status E
Job finishedDear Anthony
It is better to give version and platform details.
Have a look on 91216,586618,Let me know if u need more help.
Regards
Vinod -
BW 7.0 system copy Install Java Engine step fail
Hi, All
We perform system copy of our production BW system from DB2 9/AIX 5.3 to DB2 9/Windows 2003 for making sandox system
Migration import is fail on step Install Java Engine with error :
Extracting packed repository.
Caught OutOfMemoryError
java.lang.OutOfMemoryError
Severe (internal) error. Return code: 16
According to SAP note 1120872 i replace "-Xmx512m" by "-Xmx1024m" in control.xml file in the following lines:
var jdkArgs = installer. onOS400() ? ["-showversion", "-Xms256m", "-Xmx1536m"] : ["-showversion", "-Xmx512m"];
and restart sapinst, but this not help and this error get again
I test other values for 64,128,512,1536, 2048 but this not help
How i can workaround this error ?
Thank's
With best regards, DmitryHi,
Please check the link below.
http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_17470
Hope it helps you.
Rgds,
Suman -
Experts,
I am performing Homogeneous System copy using backup/restore method.I have taken QA system backup ie dump files and trying to build on Sandbox system for testing purpose.Everything went fine and was able to load the dump but stuck at one of the point and throwing me error
ERROR [cinstallercallbackimpl.cpp:228]
CJS-00030 Assertion failed: Execution of SQL script reports an unexpected error.
When I checked the sapinst_dev log I found the below error but not able to fix it and not aware to proceed further
1> use SID
1> EXEC sp_changedbowner sapsa
Msg 17362, Level 16, State 1:
Server 'SID', Procedure 'sp_changedbowner', Line 181:
The proposed new db owner already is a user in the database or owns the database.
(return status = 1)
I am sure these may be small changes that have to be made by changing the db owner and Im not exactly sure how to perform it.
Note:I am Using the Windows environment with Sybase ase database and SWPM tool to perform.
Appreciate your suggestions
ThanksI fixed the issue ..by changing the owner sapsa.Bingo !!!!
-
ECC 6.0 System copy export fail
WARNING 2011-12-08 21:38:22.281
Execution of the command "C:\j2sdk1.4.2_17-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.exp.ExportMonitor -sapinst" finished with return code 103. Output:
java version "1.4.2_17"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_17-b06)
Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_17-b06, mixed mode)
Export Monitor jobs: running 1, waiting 0, completed 45, failed 0, total 46.
Unloading of 'SAPAPPL0_5' export package: ERROR
Export Monitor jobs: running 0, waiting 0, completed 45, failed 1, total 46.
ERROR 2011-12-08 21:38:22.282
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) export_monitor.java.log, export_monitor.log.
ERROR 2011-12-08 21:38:22.293
FCO-00011 The step runMigrationMonitor with step key |NW_Export|ind|ind|ind|ind|0|0|NW_ABAP_Export_Dialog|ind|ind|ind|ind|4|0|NW_ABAP_Export|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) export_monitor.java.log, export_monitor.log.).
I am using SAP ECC 6.0 with Ms Sql 2005 on 64 bit windows 2008 R2 OS. During a system copy export i am getting this error.
Please help me.Your 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 -
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
Maybe you are looking for
-
I have an issue with the iMessage application on my MacBook Air. Since few weeks ago I have been able to receive few messages but I'am unable to respond or send messages. Everytime I try an exclamation mark appears I've tried to initialize the operat
-
HT204053 Can you use Icloud with a Windows 7 PC?
Please can I have some help - I wish to use Icloud on my PC but cannot find any help - all suggestion would be appreciated - even if it is to say - Impossible
-
When I start my iPhoto it says: "Your photo library is either in use by another application or has become unreadable". I don't have a back-up of my library and I don't know what to do! Thanks
-
Anyone having problems downloading movies to a PC?
Is anyone having a problem downloading movies to a windows 7 PC?
-
Hi There! I am using RPC to group multiple DML to a particular database instead of multiple database trips.Does calls to various RPC's from one BEGIN END block from local database will gurantee the two phase commit?? regards. Sanjeeb Bose HCL Infosys