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

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

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

Similar Messages

  • System copy errors during ABAP export ECC 5.0

    Hi
    I'm need to do system system copy for our ECC 5.0 system on Win/ora platform. I have followed the system copy document from SMP. I'm getting the below error while exporting the ABAP schema. Could someone guide me on how to fix this.
    ERROR 2008-12-25 11:32:27
    MSC-01015  Process finished with error(s), check log file C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPCLUST.log
    =======================
    (NT)  Error:  AABLG: normal NameTab from 20050112230750 younger than alternate NameTab from 20000323230317!
    (SYSLOG) INFO: k CQF : AABLG&20000323230317&20050112230750&                 rscpgdio 47
    (RSCP) ERROR: -
    3-
    (RSCP) ERROR: code:   64  RSCPECALL   
    (RSCP) ERROR: Altername NameTab too old                                          
    (RSCP) ERROR: module: rscpgdio location:   47 line:  3007
    (RSCP) ERROR: TSL01: CQF  p3: AABLG&20000323230317&20050112230750&      
    (RSCP) ERROR: -
    myCluster (55.20.Exp): 924: received return code 64 from rscpCheckNTTimeStamps.
    myCluster (55.20.Exp): 925: suspicious create timestamp of alternate nametab encountered.
    myCluster (55.20.Exp): 929: create timestamps of nametab: 20050112230750; alternate nametab: 20000323230317.
    myCluster (55.20.Exp): 299: error when retrieving physical nametab for table AABLG.
    (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
    ======================
    ERROR 2008-12-25 11:32:27
    MSC-01015  Process finished with error(s), check log file C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPPOOL.log
    ===========================
    (NT)  Error:  AT01: normal NameTab from 20050112234859 younger than alternate NameTab from 20011002204708!
    (SYSLOG) INFO: k CQF : AT01&20011002204708&20050112234859&                  rscpgdio 47
    (CNVPOOL) Altername NameTab too old AT01&20011002204708&20050112234859&   Abort.
    (CNVPOOL) conversion failed for row 0 of table  VARKEY = 010100                                           
    (CNV) ERROR: data conversion failed.  rc = 2
    (RSCP) INFO: environemnt variable "I18N_POOL_WIDTH" is not set. Checks are active.
    (RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
    =========================
    ERROR 2008-12-25 11:32:27
    MSC-01015  Process finished with error(s), check log file C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPSSEXC.log
    ===========================
    (NT)  Error:  DOKCLU: normal NameTab from 20050112230750 younger than alternate NameTab from 20000323224119!
    (SYSLOG) INFO: k CQF : DOKCLU&20000323224119&20050112230750&                rscpgdio 47
    (RSCP) ERROR: -
    3-
    (RSCP) ERROR: code:   64  RSCPECALL   
    (RSCP) ERROR: Altername NameTab too old                                          
    (RSCP) ERROR: module: rscpgdio location:   47 line:  3007
    (RSCP) ERROR: TSL01: CQF  p3: DOKCLU&20000323224119&20050112230750&      
    (RSCP) ERROR: -
    myCluster (55.20.Exp): 924: received return code 64 from rscpCheckNTTimeStamps.
    myCluster (55.20.Exp): 925: suspicious create timestamp of alternate nametab encountered.
    myCluster (55.20.Exp): 929: create timestamps of nametab: 20050112230750; alternate nametab: 20000323224119.
    myCluster (55.20.Exp): 299: error when retrieving physical nametab for table DOKCLU.
    (CNV) ERROR: data conversion failed.  rc = 2
    (RSCP) INFO: I18N_NAMETAB_TIMESTAMPS not in env: checks are ON (Note 738858)
    ========================
    ERROR 2008-12-25 11:32:27
    MSC-01015  Process finished with error(s), check log file C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPSDIC.log
    ========================
    (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
    =======================
    Thanks & Regards
    Jagan

    C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPCLUST.log
    C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPPOOL.log
    C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPSSEXC.log
    C:\Program Files\sapinst_instdir\ECC50\COPY\EXPORT\ABAP\COPY\UC\DBEXP/SAPSDIC.log
    paste the above logs here.
    Thanks
    SM

  • Java System Copy Error

    Hi all. I am trying System Copy.
    During the Database Load I became the following Error
    "An error occurred while processing service SAP NetWeaver'04 Support Release1> Java System> MS SQL Server> Migration - Target System Installation."
    jload.log is:
    info: trying to create table IMS_SYNCINXVIEW
    com.sap.inst.jload.Jload dbImport
    info: table IMS_SYNCINXVIEW created
    com.sap.inst.jload.Jload dbImport
    warning: DB Error during import of IMS_SYNCINXVIEW
    com.sap.inst.jload.Jload printSQLException
    warning: Message: The SQL statement "INSERT INTO "IMS_SYNCINXVIEW" ("ACTIVITYID","RESOURCEID","DOCUMENTTYPE","FORMATVERSION") VALUES (?,?,?,?)" contains the semantics error[s]: table "IMS_SYNCINXVIEW" unknown
    com.sap.inst.jload.Jload printSQLException
    warning: SQLState: SAP06
    com.sap.inst.jload.Jload printSQLException
    warning: ErrorCode: 1001123
    com.sap.inst.jload.Jload dbImport
    info: trying to create table J2EE_CONFIG
    com.sap.inst.jload.Jload logStackTrace
    warning: java.nio.BufferUnderflowException
         at java.nio.Buffer.nextGetIndex(Buffer.java:404)
         at java.nio.HeapByteBuffer.getChar(HeapByteBuffer.java:234)
         at com.sap.inst.jload.io.DataFileEntry.<init>(DataFileEntry.java:52)
         at com.sap.inst.jload.io.DataFile.getNextEntry(DataFile.java:354)
         at com.sap.inst.jload.io.DataFile.findDataEntry(DataFile.java:397)
         at com.sap.inst.jload.db.DBTable.create(DBTable.java:77)
         at com.sap.inst.jload.Jload.dbImport(Jload.java:278)
         at com.sap.inst.jload.Jload.executeJob(Jload.java:397)
         at com.sap.inst.jload.Jload.main(Jload.java:621)
    com.sap.inst.jload.db.DBConnection disconnect
    info: disconnected

    Hi,
    I have also faced the same error during system copy, the tables IMS_SYNCINXVIEW, PVC_ACTVERSVIEW, PVC_OBJVERSVIEW which are related to Development Infrastructure. These are bad tables and hence it has to be removed.
    I found a file called negativTableListForJload.xml in C:\Program File
    sapinst_instdir\NW04S\LM\COPY\MSS\SYSTEM\CENTRAL\AS-JAVA\install\sltools\
    The import could be continued after removing the line
         <object name="IMS_SYNCINXVIEW" action="insert"/>
    (and of course the corresponding entries for all the other views) from
    the file IMPORT.XML
    So the steps u have to perform are
    Please cancel the Installation by pressing the cancel button and then stop the sapinst and edit these files and again continue the old installation.
    1) go to C:\Program File
    sapinst_instdir\NW04S\LM\COPY\MSS\SYSTEM\CENTRAL\AS-JAVA
    EDIT the IMPORT.XML i.e. delete the line
    <object name="IMS_SYNCINXVIEW" action="insert"/>
    2) now again got to C:\Program File
    sapinst_instdir\NW04S\LM\COPY\MSS\SYSTEM\CENTRAL\AS-JAVA\install\sltools\
    edit the negativTableListForJload.xml file. i.e. delete the lines which has the entry for these tables.
    3) Restart the installation. Donot retry.
    Reward point if u feel so.
    cheers
    Naveen.H

  • Error: ORA-01654: unable to extend index APPLSYS.SYS_IOT_TOP_34179 by 16 in

    Hi,
    I am using Oracle API (HzLocationV2Pub.LocationRec) to update record and getting the following error message in JDeveloper log and couldn't able to update.
    x_return_status : U
    x_msg_data : Unexpected SQL error encountered during synchronization:
    Procedure: sync_party_site
    Error: ORA-01654: unable to extend index APPLSYS.SYS_IOT_TOP_34179 by 16 in tablespace APPS_TS_QUEUES
    Please contact the system administrator.
    x_msg_count : 1
    What is the reason behind this error?
    How to resolve this?
    Thanks & Regards,
    Sagarika

    Hi,
    You need to add more space to your datafile/tablespace, or extend the index.
    SQL> alter index APPLSYS.SYS_IOT_TOP_34179 storage (maxextents unlimited);
    SQL> ALTER TABLESPACE <tablespace name> ADD DATAFILE '<full path and file name>' SIZE <integer> <K|M>; Note: 1025288.6 - How to Diagnose and Resolve UNABLE TO EXTEND Errors
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=1025288.6
    Note: 19049.1 - OERR: ORA 1654 unable to extend index by for tablespace
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=19049.1
    Note: 762273.1 - ORA-1654: unable to extend index
    https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=762273.1
    Regards,
    Hussein

  • [URGENT HELP] Why is cannot install Windows 7 on my X120e? ERROR : Setup was unable to create..

    i have got X120e from my college with ubuntu 11.04 installed. But my half of softwares dont work on this Lunix OS so decided to install windows 7, downloaded officially as i have keys for activation.
    I used USB drive to install, Windows 7 setup sucessfully started on boot up but its getting error
    "Setup was unable to create a new system partition or locate an existing system partition. See the Setup log files for more information"
    I have not connected any other devices.
    My Hard disk is NOT dynamic, its basic.
    I have contacted lenovo service centre, but this are taking up calls.
    I am fed up of this, please help me..
    I have exams coming and i need this urgently.
    Solved!
    Go to Solution.

    Hello,
    Do you just want to delete the Ubuntu partition?  If so, you may be able to do by booting from the Microsoft Windows 7 installation disc, pressing Shift+F10 to get to a Command Prompt, and then using the DISKPART.EXE program to erase the hard disk drive.
    Regards,
    Aryeh Goretsky
    I am a volunteer and neither a Lenovo nor a Microsoft employee. • Dexter is a good dog • Dexter je dobrý pes
    S230u (3347-4HU) • X220 (4286-CTO) • W510 (4318-CTO) • W530 (2441-4R3) • X100e (3508-CTO) • X120e (0596-CTO) • T61p (6459-CTO) • T43p (2678-H7U) • T42 (2378-R4U) • T23 (2648-LU7)
      Deutsche Community   Comunidad en Español Русскоязычное Сообщество

  • "error building executble. unable to create file."

    Hello!
    When I try to run or Build an Pocket PC application i get thes message: "error building executble. unable to create file."
    I have installed:
    LAbview 8
    Microsoft embedded visual c++ 4.0
    Microsoft Pocket PC SDK
    PDA Module 8
    Does anyone have a clue wats wrong?

    The builder is missing the C compiler and the linker from Microsoft for the emulator target.
    On my system they are located in C:\Program Files\Microsoft eMbedded C++ 4.0\EVC\wce420\bin. Check on your computer.
    I couldn't find a place where to set this path (remember: I have 7.1, 8.0 may support this settings, although it's not likely).
    Paolo
    Paolo
    LV 7.0, 7.1, 8.0.1, 2011

  • Error Code -17400; Unable to create thread

    Running TestStand 4.0.  Test sequence calls many sequences that run as new executions and runs fine for up to about 8 units testing simultaneously.  After that, I get a run-time error code -17400; Unable to create thread.  There are no other details available.  The steps that generate the error are able to create the new executions initially, but eventually fail once about 22 executions are running.  I am monitoring memory resources and there does not appear to be any issues.  Any troubleshooting suggestions?  Thanks.

    My test sequence has several test groups, each of which contain loops that create new threads (tests) for 48 UUTs.  Thus the number of running threads does get very high.  I was running into problems with Windows XP GDI Object resources once the number of threads reached about 200.  I then modified my program into smaller test groups to keep the number of threads at any time to less than 150.  GDI resources are no longer an issue, but the error -17400 unable to create thread happens after the first test group has completed and the second test group is just trying to run.  Note that the second test group runs fine if I skip the first test group, so the sequence itself should be okay.  I thought it might be a memory issue (even though there are no apparent memory issues seen in Windows Task Manager), so I set the "Unload after step executes" property for each of the new executions created.  That did not resolve the issue. 
    I am trying to create a simple sequence to duplicate the error without using any of the actual test sequences that require test hardware, but have not been successful thus far.
    Thanks for your replies and suggestions!

  • Receiving error message every time I try to create a pdf.  "An unexpected error occurred.  Unable to create .pdf"

    I just downloaded the program to a new laptop.  I "repaired, uninstalled, installed" and am still getting the error.

    Adobe Acrobat Pro AcademicMS Word (MS Office 10)  Acrobat > File > Create PDF from File
    Embrace what today offers,Helen Catrece Nosal
    "The grand essentials to happiness in this life are something to do, something to love, and something to hope for" ...Joseph Addison
          From: TanviRastogi <[email protected]>
    To: stephen nosal <[email protected]>
    Sent: Saturday, April 25, 2015 12:01 PM
    Subject:  Receiving error message every time I try to create a pdf.  "An unexpected error occurred.  Unable to create .pdf"
    Receiving error message every time I try to create a pdf.  "An unexpected error occurred.  Unable to create .pdf"
    created by TanviRastogi in Creating, Editing & Exporting PDFs - View the full discussionHi Can you please tell Acrobat version you are using, i.e, Acrobat X or Acrobat XI or Acrobat Pro DC? Also how are you trying to create PDF like from within Acrobat > File > Create PDF from File or from some Browser or from Office? Which type of file are you trying to convert - PowerPoint or Word or Excel or html file ? ThanksTanvi If the reply above answers your question, please take a moment to mark this answer as correct by visiting: https://forums.adobe.com/message/7479679#7479679 and clicking ‘Correct’ below the answer Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: Please note that the Adobe Forums do not accept email attachments. If you want to embed an image in your message please visit the thread in the forum and click the camera icon: https://forums.adobe.com/message/7479679#7479679 To unsubscribe from this thread, please visit the message page at , click "Following" at the top right, & "Stop Following" 
    Start a new discussion in Creating, Editing & Exporting PDFs by email or at Adobe Community For more information about maintaining your forum email notifications please go to https://forums.adobe.com/thread/1516624.

  • When copying pic from iPhoto 09 to a file, to burn a CD, after 35 photos it stops copying and I get "Unable to create/users/dividrublesr/ documents/I don't know what is going on.

    When copying pic from iPhoto 09 to a file, to burn a CD, after 35 photos it stops copying and I get "Unable to create/users/dividrublesr/ documents/I don't know what is going on. Forgive me for any mistakes, I am a first timer.

    Given that the file is selected then the next possibility is that you're exporting two files with the same name. When you do this the export breaks down as the second file would overwrite the first. Check the filenames.
    Regards
    TD

  • Unable to create Indexes on F table

    Hi
    We are unable to create Indexes on one of our Cube's fact table...I tried creating with Process chain , Batch and also tried with SE11 ...table name ... Indexes ...Activate...
    Its showing active object generated but the warning msg Index does not exist in database system MSSQL still exist  and not creating indexes...When I activate the indexes its not showing this warning for all other cubes...Please advice
    regards

    Hi Sam,.
    The index creation on F table is taken care by the system itself. When you activate the cube, the DIM and F table are created and at the same time, indexes are created.
    To create your own indes, though, go to se11...>F Table name-->Indeexes-it will show you system created indexes.
    There will be a create sign....click there... and give the name of the index(like 1, 2). It will open up the maintain index page, where you have to mention all the parameter.
    Thanbks...
    Shambhu

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

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

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

  • SAP system copy error

    Hi Experts,
    I am currently facing an issue/error while doing a homogeneous system copy with SAP NW 7.4 (SAP ERP 6.0 Ehp7) servers. Both source and target systems are test/demo servers and system copy procedure needs to be established as a part of implementation.
          An error occurred while processing option SAP Business Suite 7i 2013 Support Release 1 > EHP7 for SAP ERP 6.0 ABAP Support Release 1 > SAP ASE > System Copy > Target System > Standard System > Based on AS ABAP > Database Refresh or Move( Last error reported by the step: Assertion failed: Unable to load database RD3. Refer to trace file sapinst_dev.log for further information.)
    Sybase ASE version = 15.7_122
    sapinst_dev log file description -
    Error description (sapinst_dev log file) –
    Execution of the command "isql64 -e -w999 -Usa -SSAP-PROD-TEST:4901 -X" finished with return code 0. Output:
    Password:
    1> use master
    1> load database RD3
    2>  from 'F:/Backup_RD1_04042015/rd1_s1.dmp' stripe on 'F:/Backup_RD1_04042015/rd1_s2.dmp' stripe on 'F:/Backup_RD1_04042015/rd1_s3.dmp'
    Backup Server session id is: 33. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.
    Backup Server: 6.28.1.1: Dumpfile name 'RD11509409BE6    ' section number 1 mounted on disk file 'F:/Backup_RD1_04042015/rd1_s3.dmp'
    Backup Server: 6.28.1.1: Dumpfile name 'RD11509409BE6    ' section number 1 mounted on disk file 'F:/Backup_RD1_04042015/rd1_s1.dmp'
    Backup Server: 6.28.1.1: Dumpfile name 'RD11509409BE6    ' section number 1 mounted on disk file 'F:/Backup_RD1_04042015/rd1_s2.dmp'
    Msg 3105, Level 16, State 4:
    Server 'RD3', Line 1:
    Data on dump will not fit into current database. Need 101376 Mbyte database.
    1> online database RD3
    Msg 930, Level 14, State 1:
    Server 'RD3', Line 1:
    Database 'RD3' cannot be opened because either an earlier system termination left LOAD DATABASE incomplete or the database is created with 'for load' option. Load the database or contact a user with System Administrator (SA) role.
    No matter how much I try to execute the commands for loading database (LOAD DATABASE & ALTER DATABASE commands), i's not working. I have already added the size mentioned above. Although it still didnt work the size of the DB grew by 99GB (displayed in the incresed size of F: drive in Windows.server 2012 r2 OS level.
    Any help leading to closure of this error is highly appreciated. I have attached all necessary screenshots for your kind reference.
    Thanks and regards,
    M. Nizam

    Hi Nizamuddin,
    Message text
    Data on dump will not fit into current database. Need %d Mbyte database.
    Explanation
    This error occurs when an attempt is made to load a database dump into a database smaller than the dumped database. You cannot use dump database or load database to shrink a database, regardless of the amount of actual data in the database.
    Action
    If your goal is to load the database from the dump, you must increase the size of the database being loaded into to at least the configured size of the dumped database. You can do this with either the alter database command or by dropping and re-creating a larger database.
    If your goal is to shrink the total size of a database, you cannot use dump and load. You must copy all the data out of the database using bcp, drop the database and re-create a smaller database, then re-create the database structure with scripts, and reload the data with bcp.
    extend your current master *database* on the master *device* to a total size of 101376MB(or more) (use  'alter database' command)
    alter database master on master = <size in MB>
    If there isn't enough room on the master device AND the master device is either a file system device in a file system that has free space or was created on a raw partition that is actually larger than the master device was defined, then you can use the DISK RESIZE command to enlarge the master device
    disk resize name = "master", size = <additional space in MB>
    Regards,
    V Srinivasan

  • R3load system copy: Error on database export

    Hello all,
    I am trying to do a system copy via r3load - Export and then import on a WAS 640 oracle Netweaver based system which has both ABAP and JAVA stack. The source and target system are on the same win2000 host. I am getting below errors in the export stage of the system copy. I am following the sap doc: Homogeneous and Heterogeneous System Copy for SAP Systems based on SAP Web AS ABAP 6.40 SR1 .pdf
    As per the doc the below are the main steps
    1) Generate DLL-statements [Page 55] (Call transaction SE38 and run the program SMIGR_CREATE_DDL...Execute the program. The DDL statements are generated and are written to thespecified directory.)
    2) Run SAPinst to export the database [Page 48].
    3) Set up the target system [Page 60].
    I am stuck at 2) with the below errors during the export.
    For step 2, the sapinst asked me to enter
    source <SID>
    Source <DBSID>
    Source schema: I gave this as SAP<SID>
    no of process and alphabetic load.
    Afer this...
    R3ldctlExport.log reports the below errors
    WARNING: no technical settings for table "WFQUE" in SAP data dictionary - defaults used
    WARNING: no technical settings for table "WFSTO" in SAP data dictionary - defaults used
    WARNING: value for DD28S.CONSTANTS not in quotes, view "COVMVSVW"
    WARNING: value for DD28S.CONSTANTS not in quotes, view "DVTOPAY"
    WARNING: value for DD28S.CONSTANTS not in quotes, view "V_LTDX"
    WARNING: value for DD28S.CONSTANTS not in quotes, view "W3TEMPLATE"
    DbSl Trace: ORA-24508 occured when executing SQL statement (parse error offset = 29)
    ERROR: ExeRead for get_loc_table_inf failed
    ORA-24508: Message 24508 not found;  product=RDBMS; facility=ORA
    Error generating DDLINF.TPL
    (UPT) Info: Preparing tables and tablespace entries.
    (UPT) Info: Distributing tables and tablespace entries.
    (WLL) Info:  finished writing location lists
    And sapinst reports several of the below errors...
    ERROR 2007-06-17 17:24:14
    MSC-01015  Process finished with error(s), check log file D:\Program Files\sapinst_instdir\NW04SR1\WEBAS_ABAP_ORA_UC\EXP/SAPUSER.log
    ERROR 2007-06-17 17:22:44
    MSC-01015  Process finished with error(s), check log file D:\Program Files\sapinst_instdir\NW04SR1\WEBAS_ABAP_ORA_UC\EXP/SAPDODS.log
    ERROR 2007-06-17 17:22:44
    MSC-01015  Process finished with error(s), check log file D:\Program Files\sapinst_instdir\NW04SR1\WEBAS_ABAP_ORA_UC\EXP/SAPPOOL.log
    ERROR 2007-06-17 17:22:44
    MSC-01015  Process finished with error(s), check log file D:\Program Files\sapinst_instdir\NW04SR1\WEBAS_ABAP_ORA_UC\EXP/SAPSDIC.log
    ...etc
    *.TSK files are being created.
    For example, if I describe for one particular package...
    SAPSSEXC.TSK has entries like the below
    D DM45T E ok
    D DM46S E ok
    D DOKCLU E err
    D DOKHL E xeq
    D DOKIL E xeq
    D DSYST E xeq
    D DYNPSOURCE E xeq
    D ENLFDIR E xeq
    D EUDB E xeq
    D EUGUITEXT E xeq
    D EUOBJ E xeq
    D EUOBJEDIT E xeq
    A log file SAPSSEXC.log exists which notes the termination of the r3load export process.
    EXP) TABLE: "DM42S"
    (EXP) TABLE: "DM42T"
    (EXP) TABLE: "DM43T"
    (EXP) TABLE: "DM45L"
    (EXP) TABLE: "DM45T"
    (EXP) TABLE: "DM46S"
    (NT)  Error:  DOKCLU                        : normal NameTab from 20041108162211 younger than alternate NameTab from 20010201171049!
    Syslog: k CQF : DOKCLU                        &20010201171049&2004110rscpgdio 47myCluster (55.13.Exp): 874: received return code 64 from rscpCheckNTTimeStamps.
    myCluster (55.13.Exp): 875: suspicious create timestamp of alternate nametab encountered.
    myCluster (55.13.Exp): 879: create timestamps of nametab: 20041108162211; alternate nametab: 20010201171049.
    myCluster (55.13.Exp): 297: error when retrieving physical nametab for table DOKCLU.
    (CNV) ERROR: code page conversion failed
                 rc = 2
    .--============.|                              RSCP - Error                            || Error from:             Codepage handling (RSCP)                   3 || code:   64  RSCPECALL    Illegal mixture of procedure calls.         || Altername NameTab too old                                            || module: rscpgdio no:   47 line:  2876                    T100: TS007 || TSL01: CQF  p3: DOKCLU                        &20010201171049&2004110||                                                                      |`--
    '(rscpMC) Warn: env I18N_NAMETAB_TIMESTAMPS not set
    (DB) INFO: disconnected from DB
    I:\usr\sap\VIK\SYS\exe\run/R3load.exe: job finished with 1 error(s)
    I:\usr\sap\VIK\SYS\exe\run/R3load.exe: END OF LOG: 20070617185123
    Also some of the other log files for other packages terminate with:" disconnected from db" in the middle of the export.
    What I tried: I tried putting in the latest patch level for r3ldctl, r3load and r3szchk kernel files. It was at kernel patch 43. I upgraded to latest 175 from market place. And restarted sapinst again to start the export again. Again I face the same problem. Sapinst aborts at this stage again. I basically took the whole sapexedb patch 175 and yupdated the kernel but it did not help.
    If any of you out there can lead me in the right direction so that I can get over this stumbling block, would be grateful.
    Many Thanks, Vikram
    [email protected]

    Could anybody  please tell what is the required codepage for oracle?
    Our system has NLS_LANG=AMERICAN_AMERICA.WE8DEC
    Thanks a lot!

  • Hom System Copy- Error running J2ee migration tool kit

    Good Day Guys,
    Im performing homogenous system copy.I have encountered below error:
    INFO 2008-10-20 13:05:33
    Output of C:\j2sdk1.4.2_18-x64\bin\java.exe -classpath D:/usr/sap/LE1/SYS/global/sltools/sharedlib/launcher .jar;. com.sap.engine.offline.OfflineToolStart com.sap.sdt.jmt.migrationtool.MigrationToolImport D:/usr/sap/LE1/SYS/global/sltools/jmt;D:/usr/sap/LE1 /SYS/global/sltools/sharedlib import.switch resume downtime mti.properties is written to the logfile C:/Program Files/sapinst_instdir/ERP/LM/COPY/MSS/SYSTEM/CENTRA L/AS/runJmt.log.
    WARNING 2008-10-20 13:05:34
    Execution of the command "C:\j2sdk1.4.2_18-x64\bin\java.exe -classpath D:/usr/sap/LE1/SYS/global/sltools/sharedlib/launcher .jar;. com.sap.engine.offline.OfflineToolStart com.sap.sdt.jmt.migrationtool.MigrationToolImport D:/usr/sap/LE1/SYS/global/sltools/jmt;D:/usr/sap/LE1 /SYS/global/sltools/sharedlib import.switch resume downtime mti.properties" finished with return code 27. Output:
    ERROR 2008-10-20 13:05:34
    CJS-20068 Error when running the J2EE Migration Toolkit.<br>SOLUTION: See output of logfile C:\Program Files/sapinst_instdir/ERP/LM/COPY/MSS/SYSTEM/CENTRA L/AS//runJmt.log: ''.
    ERROR 2008-10-20 13:05:34
    CJS-20068 Error when running the J2EE Migration Toolkit.<br>SOLUTION: See output of logfile C:\Program Files/sapinst_instdir/ERP/LM/COPY/MSS/SYSTEM/CENTRA L/AS//runJmt.log: ''.
    ERROR 2008-10-20 13:05:34
    FCO-00011 The step RunMigrationController with step key |NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_One host_System|ind|ind|ind|ind|1|0|NW_CI_Instance|ind |ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|in d| ind|ind|ind|4|0|NW_RUN_MIGRATION_CONTROLLER|ind|ind |ind|ind|2|0|RunMigrationController was executed with status ERROR .
    INFO 2008-10-20 13:06:29
    An error occured and the user decide to stop.\n Current step "|NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_On ehost_System|ind|ind|ind|ind|1|0|NW_CI_Instance|in d|ind|ind|ind|11|0|NW_CI_Instance_Configure_Java|i nd|ind|ind|ind|4|0|NW_RUN_MIGRATION_CONTROLLER|ind |ind|ind|ind|2|0|RunMigrationController".
    I have checked the runjmt.log its empty.
    I did find a note 966752.but couldnt solve the problem.Another thing do we need to have same version of j2sdk,mine are different on source(ia64) and target(x64).
    Please advice.
    BasisNerd

    CAn you precise also what Migration tool are you using?
    Migration from 5.1 to SAP BPC 7.0 NW?
    In that case when you are speaking about the installation about what part are you speaking?
    I think actually you are speaking about the migration tool from 4.2 to 7.0 Microsoft version .
    In that case you can install the mIgration tool just with SAP BPC sys admin users and you have to input the password for that user. Sys admin user for BPC is usually the user used for installation of SAP BPC server.
    Any way I suggest to follow the Migration tool training document and there you will find all the information necessary.
    Regards
    Sorin Radulescu

  • System Copy Error @ CreateDB using control.sql file

    Hi Experts,
    I am doing A Homogeneous System Copy. I have installed DB and patched 10.2.0.2 as source is of the same level.
    After DB Installation, restored DB , run the control.sql file and opened it. Recovered DB using this way: "Recover Database using backup controlfile until cancel;" and opened reset logs
    Once DB is open, i continued other steps from the point Backup/Restore DB in sapinst. It said CONTROL.SQL file is missing, so i have placed the same in installation directory. In this step "CREATE DATABASE with control.sql file" it has been throwing me error:  Ora-00265 instance recovery required, cannot set ARCHIVE log mode DB altered. DB Closed. DB Dismounted and DB Closed.
    Could you please explain why it is asking for Archive logs and shutting down the DB.
    Thanks,
    Subbu

    Hi,
    well the copy guide says you have to do an OFFLINE backup.
    So sapinst expects a restored database (from offline backup) with non existing controlfiles
    and the need to do a CREATE CONTROLFILE ...
    You already did that manually. You already opened the db...
    So there is no way to run a CREATE CONTROLFILE with "SET database" (not sure
    about the RESETLOGS in this case for a second time...).
    I do not know what state your DB is in right now. If it is completely operational
    and fully recovered and can be opened and shutdown normal, try to substitute
    your control.sql with simply (copy the original content somewhere else)
    alter database mount;
    alter database open;
    Repeat the sapinst step.
    Depending on how far it put in the progress bars in the xml file, you might need
    only one of those two statements in control.sql.
    If the restored DB is not operational now, then the controlfiles might be garbled due to the
    second try top create them from sapinst. Not sure what the situation is then.
    Volker

Maybe you are looking for

  • Getting error in ADF Login security

    Hi Team, I am making security login mechanism. I referred - Oracle ADF 11g Security - Custom ADF Login Form - Part 1 (High) and part 2 video from youtube. I am not getting any error in my log but after entering username and password its giving me err

  • Re: SQL Database

    What would you recommend for a SQL database managment system with Coldfusion? Assuming I am on a windows-based computer

  • MS Project 2013 - Report Page Setup Bug

    Hello When I create a report in MS Project, for example a cash flow, I will setup the header and footer then save and print the file. When I return the gannt chart view or any other view then return to the report and re-print, the header and footer i

  • Have songs duplicated on phone how do i remove

    I have songs on my Iphone that say are linked to a url how do i get rid of them as the screw up my shuffle

  • JPanel doesn't paint graphics

    Hi ! I've been writing a program that should graph a linear function, the problem is that I'm trying to draw a line in a JPanel but this doesn't work XD...The program has 2 windows. The first one is the windows from where i get data for the function,