System Copy need hlep

Hi Alls,
I want to System copy PI-QA system to PI-DEV system with database, we have PI-7.0, under windows 2003 patch level 16 and kernal 159 Oracle database...
SAP services help, is very details and more then 150 pages, I would like to know just Step by Step procedure... I know you guys very helpful and you can take little time to writedown Step by Step procedure... will be really appricated...
Thanks again in Advanced...
Angeline

I know you guys very helpful and you can take little time to writedown Step by Step procedure
Nope... this is not how it works!
You're meant to read those 150 pages and if you have any questions post here... this is a discussion forum not a do my job for me forum. The documentation you downloaded from SAP Marketplace is accurate and anything different than that doesnt guarantee that at the end of the process SAP will support your system.
Read the "Rules of Engagement"
Regards
Juan

Similar Messages

  • MCOD system copy - need help with plan

    Hi all,
    I got to do export-import for my customer and am facing an issue with their CRM system.
    the source
    MCOD with crm 7.0 abap lets say <sid>=abc and crm 7.0 java <sid>=xyz.
    (netweaver ehp1, hence the split stack)
    DB is Oracle and OS windows.
    target
    i have currently installed crm 7.0 abap on oracle and linux.
    now, here is my plan...  please do let me know your thoughts.
    1.) i will install CRM 7.0 java in target as mcod
    2.) export AS ABAP from source
    3.) export AS JAVA from source
    4.) import AS ABAP into target
    5.) import AS JAVA into target with option mcod.
    well, my question here is during the export will i be able to get 2 exports? i mean will inst export the 2 schemas seperately or there is just option for 1 export and thats the whole database?
    awating your opinions
    Regards,

    hi Shanser,
    if its a dual stack installation you can just run one time SAPINST to get the single export dumps,but if you have done a  add-on Java installation for your CRM system you have to execute two times the SAPINST to get the separate exports for ABAP and JAVA ,but even if you have done  the add-on installation or simple dual stack installation from DB point of view JAVA always goes to SAP<SID>DB and ABAP goes to SAP<SID> DB schema
    hope I have answered your Question
    thanks
    George

  • System Copy XI 3.0 - do I need a new SLD?

    I am planning to refresh my Sandpit XI system from my Development environment on XI 3.0, WAS 6.40, NW04.  I have the system copy guide version 1.1 which states that I need to migrate to a new SLD.  At present, I have one SLD for my Sandpit / Dev /QA environments and a second for Prd.
    The documentation explicitly states that I have to migrate to a new SLD, but I don't really want to have to maintain another one.  Has anyone experience of this?  And do I really need to create a new SLD for this.?
    Thanks in advance.
    Graham

    Graham,
          If your present Sandpit and Dev SLD's are same and you are trying to refresh sandpit with Dev, in this case it is not required to create new SLD.
    Regards,
    Ranjeeth.

  • NW04 system copy : we only need the abap stack

    Hello,
    We have a BW 3.5 Production environnement :
    Netweaver 04
    Oracle 9.2
    ABAP + JAVA stack have been initially installed on the same server but the java instance parameters have been since deactivated. The Java stack has never been used.
    Now, we're planning to install the same BW 3.5 QAS environnement (only the abap stack), configure it, and afterwards perform a typical homogeneous system copy (backup/restore) from the production environnement.
    Since we don't need at all the java part, do you think that could work ? Is there any risk of inconsistency ?
    Or do we have to install double a stack QAS enviroonement and then perform the system copy based on sapinst
    Thank you in advance for your help.
    Regards.

    You will have to perform following  steps
    1. Export the CI system on Source system
    2.  Clone the source Database to Target database. We have used IBM's Flash copy tool to accomplish that.
    3. On target install SCS , restore the DB and then import CI.
    We also have dual stack in ECC Production environment and we don't use JAVA as much.
    If you have any more questions, please let me know.
    Thanks
    Sumit Mathur

  • MIGEXPORT needed for SWPM MaxDB system copy?

    After executing a MaxDB backup/restore system copy with SWPM, there's a request for MIGEXPORT - any idea which media I shall provide?

    Hi,
    same problem. Newest SWPM, Backup/Restore Option, stopped for manual actions, now SWPM wants MIGEXPORT, but I have no export. Cannot continue,
    Started SWPM again, but it wants this media.
    Any solution here?
    Need this System tomorrow! Any idea here?
    Thanks
    Thomas

  • Homogeneous System Copy Steps Needed.

    Hi! Gurus,
    Can you please help me by <b>providing details (step by step)procedure for Homogeneous System Copy for R/3 4.7 (Kernel 620 NU) on Windows /Oracle. </b>
    I have to migrate my system from existing Server to a new Server.
    Thanks and regards,
    Pratip

    Hello Pratip,
    I consider that at u r side also there r 2 systems....source and destination...
    also Source and destination both are on the same O.S. & D.B level..this is the primary condition for that.............
    Here i will show u the steps using Online bakcup
    (1) Take a online backup of source along with the Archies generated during Hotbackup
    (2) create control file from source system and edit it to use for the new sysem.....For setting the SID and Archivlogmode...
    (3)copy entier online baclup to the same destination drives.....also archive to the destination server
    (4) replace the older controlfile with the newer generated file....mount and execute that controlfile ( e.g. abc.sql)
    (5)then start the database it will ask for archives....supply copied archive path to it...recover database using backup controlfile
    (6)start ur database with resetlog options...
    (7)then execute following sdcripts
    create user 'OPS$<Hostname>\<SID>ADM' default tablespace SYSTEM
    temporary tablespace psaptemp identified externally;
    grant connect,resource,sapdba to 'OPS$<HOSTNAME>\SAP<SID>ADM';
    create user 'OPS$<Hostname>\SAPSERVICE<SID>' default tablespace SYSTEM
    temporary tablespace psaptemp identified externally;
    grant connect,resource,sapdba to 'OPS$<hostname>\SAPSERVICE<SID>';
    create table SAPUSER
    (USERID VARCHAR2(256),PASSWD VARCHAR2(256)); //*first check for this table and delete this table and all entry first and then apply the next command for user creation OR you can say delete this table entirely and create newer one*//
    insert into SAPUSER values ('SAPMIP','micro123');//*please supply 'SAPPAP' and its coresponding password from PRDserver Please see the last screenshots for that*//
    (8)also set, DBS_ORA_SCHEMA=SAP<SID> (sid of u r source system not u r destiantion).
    Its completed...the job...
    it takes hardly two hours if u r db is of size 80GB....
    If u find it out as usefull then please give reward point..
    thanks

  • Needs link for JAVA homogenous system copy NW04 & NW04s

    hi
    I am unable to find the document for JAVA homogenous system copy for NW04 and NW04s.
    kindly plz provide the link for it
    its urgent
    thanks
    regards
    Shoeb

    Hi,
    try [http://service.sap.com|http://service.sap.com] -> Relase & Upgrade-Info -> Installation and Upgrade ...-> SAP NetWeaver -> SAP NetWeaver 7.0 -> Installation -> Installation - SAP NetWeaver Systems
    Kind Regards
    David Heidbrink

  • 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

  • Unable to log in to portal after system copy

    Good day
    I have copied my production portal system to a test system.  I am using an ECC Abap system as my user store.  The portal start successfully and I am able to access the Visual administrator.
    I am however unable to log on to the portal.  The error I get is "User authentication error".
    Below is an extract from the security log:
    #1.5#0011259C05FB0054000002F500001B9800043F56F6157AED#1195542635224#/System/Security/Authentication#sap.com/irj#com.sap.engine.services.security.authentication.logincontext#Guest#0##sapsep.sap.lonmin_SEP_32623050#Guest#af93b280973711dc980a0011259c05fb#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.FAILED
    User: N/A
    Authentication Stack: ticket
    Login Module                                                            Flag        Initialize  Login      Commit     Abort      Details
    com.sap.security.core.server.jaas.EvaluateTicketLoginModule             SUFFICIENT  ok          false      false      true      
    com.sap.security.core.server.jaas.CreateTicketLoginModule               SUFFICIENT  ok          false      false      true      
    com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule   REQUISITE   ok          true       true       true      
    com.sap.security.core.server.jaas.CreateTicketLoginModule               REQUISITE   ok          true       exception  true       null#
    #1.5#0011259C05FB0054000002F700001B9800043F56F61580BC#1195542635240#/System/Security/Audit#sap.com/irj#com.sap.security.core.util.SecurityAudit#Guest#0##sapsep.sap.lonmin_SEP_32623050#Guest#af93b280973711dc980a0011259c05fb#SAPEngine_Application_Thread[impl:3]_35##0#0#Warning#1#com.sap.security.core.util.SecurityAudit#Plain###Guest     | LOGIN.ERROR     | null     |      | Login Method=[default], UserID=[oostw], IP Address=[172.27.2.137], Reason=[Access Denied.]#
    Please can someone assist.
    Thanks
    Wilhelm

    Hello!
    It looks like your system is configured for ticket authentication. As you did a system copy the SSO-ticket might not be working anymore. If this is the case you need fix the SSO or you need to re-configure your Portal (at least temporarily) to allow other authentication methods (like basic password authentication).
    You can configure the order of the authentication methods in VisualAdmin and set the 'levels' (Required/Sufficient/etc.) there as well.
    Hope this helps,
    Jörg

  • System Copy Import Error

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

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

  • Error in import abap step while importing system copy.

    Hi All,
    My colleague had taken System copy of development server, few days back. it was completed successfully,
    now we want to restore that system copy, as hardware failed. But when we start the import of system copy,
    all ABAP jobs are failing in import abap step, Some DDL statement problem. can u pls help wht to do.
    I found in some forums, SMIGR_create_DDL report need to be generated prior to taking system copy, but he
    didnt taken tht.
    OS: Windows 2003
    DB: DB2
    Pls find sapinst.log
    INFO 2009-10-27 10:43:06.890
    Output of C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst is written to the logfile import_monitor.java.log.
    WARNING 2009-10-27 10:53:37.125
    Execution of the command "C:\j2sdk1.4.2_13-x64\bin\java.exe -classpath migmon.jar -showversion -Xmx1024m com.sap.inst.migmon.imp.ImportMonitor -sapinst" finished with return code 103. Output:
    java version "1.4.2_13"
    Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)
    Java HotSpot(TM) 64-Bit Server VM (build 1.4.2_13-b06, mixed mode)
    Import Monitor jobs: running 1, waiting 63, completed 0, failed 0, total 64.
    Import Monitor jobs: running 2, waiting 62, completed 0, failed 0, total 64.
    Import Monitor jobs: running 3, waiting 61, completed 0, failed 0, total 64.
    Loading of 'DOKCLU' import package: ERROR
    Import Monitor jobs: running 2, waiting 61, completed 0, failed 1, total 64.
    Loading of 'D010TAB' import package: ERROR
    Import Monitor jobs: running 1, waiting 61, completed 0, failed 2, total 64.
    Loading of 'REPOSRC' import package: ERROR
    Import Monitor jobs: running 0, waiting 61, completed 0, failed 3, total 64.
    Import Monitor jobs: running 1, waiting 60, completed 0, failed 3, total 64.
    Import Monitor jobs: running 2, waiting 59, completed 0, failed 3, total 64.
    Import Monitor jobs: running 3, waiting 58, completed 0, failed 3, total 64.
    Loading of 'DYNPSOURCE' import package: ERROR
    Import Monitor jobs: running 2, waiting 58, completed 0, failed 4, total 64.
    Loading of 'SAPAPPL1_4' import package: ERROR
    Import Monitor jobs: running 1, waiting 58, completed 0, failed 5, total 64.
    Loading of 'SAPAPPL2_2' import package: ERROR
    Import Monitor jobs: running 0, waiting 58, completed 0, failed 6, total 64.
    Import Monitor jobs: running 1, waiting 57, completed 0, failed 6, total 64.
    Import Monitor jobs: running 2, waiting 56, completed 0, failed 6, total 64.
    Import Monitor jobs: running 3, waiting 55, completed 0, failed 6, total 64.
    Loading of 'SAPNTAB' import package: ERROR
    Import Monitor jobs: running 2, waiting 55, completed 0, failed 7, total 64.
    Loading of 'SAPSSEXC_9' import package: ERROR
    Import Monitor jobs: running 1, waiting 55, completed 0, failed 8, total 64.
    Loading of 'SAPSSEXC_8' import package: ERROR
    Import Monitor jobs: running 0, waiting 55, completed 0, failed 9, total 64.
    Import Monitor jobs: running 1, waiting 54, completed 0, failed 9, total 64.
    Import Monitor jobs: running 2, waiting 53, completed 0, failed 9, total 64.
    Import Monitor jobs: running 3, waiting 52, completed 0, failed 9, total 64.
    Loading of 'SAPAPPL2_6' import package: ERROR
    Import Monitor jobs: running 2, waiting 52, completed 0, failed 10, total 64.
    Loading of 'SAPAPPL1_3' import package: ERROR
    Import Monitor jobs: running 1, waiting 52, completed 0, failed 11, total 64.
    Loading of 'SAPAPPL2_5' import package: ERROR
    Import Monitor jobs: running 0, waiting 52, completed 0, failed 12, total 64.
    Import Monitor jobs: running 1, waiting 51, completed 0, failed 12, total 64.
    Import Monitor jobs: running 2, waiting 50, completed 0, failed 12, total 64.
    Import Monitor jobs: running 3, waiting 49, completed 0, failed 12, total 64.
    Loading of 'D010INC' import package: ERROR
    Import Monitor jobs: running 2, waiting 49, completed 0, failed 13, total 64.
    Loading of 'SAPAPPL1_2' import package: ERROR
    Import Monitor jobs: running 1, waiting 49, completed 0, failed 14, total 64.
    Loading of 'SAPAPPL1_7' import package: ERROR
    Import Monitor jobs: running 0, waiting 49, completed 0, failed 15, total 64.
    Import Monitor jobs: running 1, waiting 48, completed 0, failed 15, total 64.
    Import Monitor jobs: running 2, waiting 47, completed 0, failed 15, total 64.
    Import Monitor jobs: running 3, waiting 46, completed 0, failed 15, total 64.
    Loading of 'SAPSSEXC_2' import package: ERROR
    Import Monitor jobs: running 2, waiting 46, completed 0, failed 16, total 64.
    Loading of 'DYNPLOAD' import package: ERROR
    Import Monitor jobs: running 1, waiting 46, completed 0, failed 17, total 64.
    Loading of 'SAPSSEXC_5' import package: ERROR
    Import Monitor jobs: running 0, waiting 46, completed 0, failed 18, total 64.
    Import Monitor jobs: running 1, waiting 45, completed 0, failed 18, total 64.
    Import Monitor jobs: running 2, waiting 44, completed 0, failed 18, total 64.
    Import Monitor jobs: running 3, waiting 43, completed 0, failed 18, total 64.
    Loading of 'SAPSDIC' import package: ERROR
    Import Monitor jobs: running 2, waiting 43, completed 0, failed 19, total 64.
    Loading of 'SAPAPPL2_14' import package: ERROR
    Import Monitor jobs: running 1, waiting 43, completed 0, failed 20, total 64.
    Loading of 'SAPAPPL0_2' import package: ERROR
    Import Monitor jobs: running 0, waiting 43, completed 0, failed 21, total 64.
    Import Monitor jobs: running 1, waiting 42, completed 0, failed 21, total 64.
    Import Monitor jobs: running 2, waiting 41, completed 0, failed 21, total 64.
    Import Monitor jobs: running 3, waiting 40, completed 0, failed 21, total 64.
    Loading of 'SAPSSEXC_3' import package: ERROR
    Import Monitor jobs: running 2, waiting 40, completed 0, failed 22, total 64.
    Loading of 'SAPSSEXC_4' import package: ERROR
    Import Monitor jobs: running 1, waiting 40, completed 0, failed 23, total 64.
    Loading of 'SAPAPPL2_10' import package: ERROR
    Import Monitor jobs: running 0, waiting 40, completed 0, failed 24, total 64.
    Import Monitor jobs: running 1, waiting 39, completed 0, failed 24, total 64.
    Import Monitor jobs: running 2, waiting 38, completed 0, failed 24, total 64.
    Import Monitor jobs: running 3, waiting 37, completed 0, failed 24, total 64.
    Loading of 'SAPSSEXC_7' import package: ERROR
    Import Monitor jobs: running 2, waiting 37, completed 0, failed 25, total 64.
    Loading of 'SAPAPPL0_7' import package: ERROR
    Import Monitor jobs: running 1, waiting 37, completed 0, failed 26, total 64.
    Loading of 'SAPAPPL0_1' import package: ERROR
    Import Monitor jobs: running 0, waiting 37, completed 0, failed 27, total 64.
    Import Monitor jobs: running 1, waiting 36, completed 0, failed 27, total 64.
    Import Monitor jobs: running 2, waiting 35, completed 0, failed 27, total 64.
    Import Monitor jobs: running 3, waiting 34, completed 0, failed 27, total 64.
    Loading of 'SAPAPPL2_7' import package: ERROR
    Import Monitor jobs: running 2, waiting 34, completed 0, failed 28, total 64.
    Loading of 'SAPAPPL2_4' import package: ERROR
    Import Monitor jobs: running 1, waiting 34, completed 0, failed 29, total 64.
    Loading of 'SAPAPPL1_6' import package: ERROR
    Import Monitor jobs: running 0, waiting 34, completed 0, failed 30, total 64.
    Import Monitor jobs: running 1, waiting 33, completed 0, failed 30, total 64.
    Import Monitor jobs: running 2, waiting 32, completed 0, failed 30, total 64.
    Import Monitor jobs: running 3, waiting 31, completed 0, failed 30, total 64.
    Loading of 'SAPAPPL0_3' import package: ERROR
    Import Monitor jobs: running 2, waiting 31, completed 0, failed 31, total 64.
    Loading of 'SAPCLUST' import package: ERROR
    Import Monitor jobs: running 1, waiting 31, completed 0, failed 32, total 64.
    Loading of 'SAPAPPL0_8' import package: ERROR
    Import Monitor jobs: running 0, waiting 31, completed 0, failed 33, total 64.
    Import Monitor jobs: running 1, waiting 30, completed 0, failed 33, total 64.
    Import Monitor jobs: running 2, waiting 29, completed 0, failed 33, total 64.
    Import Monitor jobs: running 3, waiting 28, completed 0, failed 33, total 64.
    Loading of 'SAPSSRC' import package: ERROR
    Import Monitor jobs: running 2, waiting 28, completed 0, failed 34, total 64.
    Loading of 'ENHOBJCONTRACT' import package: ERROR
    Import Monitor jobs: running 1, waiting 28, completed 0, failed 35, total 64.
    Loading of 'SAPAPPL0_4' import package: ERROR
    Import Monitor jobs: running 0, waiting 28, completed 0, failed 36, total 64.
    Import Monitor jobs: running 1, waiting 27, completed 0, failed 36, total 64.
    Import Monitor jobs: running 2, waiting 26, completed 0, failed 36, total 64.
    Import Monitor jobs: running 3, waiting 25, completed 0, failed 36, total 64.
    Loading of 'SAPSSEXC_1' import package: ERROR
    Import Monitor jobs: running 2, waiting 25, completed 0, failed 37, total 64.
    Loading of 'SAPSSEXC_6' import package: ERROR
    Import Monitor jobs: running 1, waiting 25, completed 0, failed 38, total 64.
    Loading of 'SAPAPPL2_8' import package: ERROR
    Import Monitor jobs: running 0, waiting 25, completed 0, failed 39, total 64.
    Import Monitor jobs: running 1, waiting 24, completed 0, failed 39, total 64.
    Import Monitor jobs: running 2, waiting 23, completed 0, failed 39, total 64.
    Import Monitor jobs: running 3, waiting 22, completed 0, failed 39, total 64.
    Loading of 'SAPPOOL' import package: ERROR
    Import Monitor jobs: running 2, waiting 22, completed 0, failed 40, total 64.
    Loading of 'SAPAPPL2_1' import package: ERROR
    Import Monitor jobs: running 1, waiting 22, completed 0, failed 41, total 64.
    Loading of 'SAPAPPL1_5' import package: ERROR
    Import Monitor jobs: running 0, waiting 22, completed 0, failed 42, total 64.
    Import Monitor jobs: running 1, waiting 21, completed 0, failed 42, total 64.
    Import Monitor jobs: running 2, waiting 20, completed 0, failed 42, total 64.
    Import Monitor jobs: running 3, waiting 19, completed 0, failed 42, total 64.
    Loading of 'REPOTEXT' import package: ERROR
    Import Monitor jobs: running 2, waiting 19, completed 0, failed 43, total 64.
    Loading of 'SAPAPPL0_5' import package: ERROR
    Import Monitor jobs: running 1, waiting 19, completed 0, failed 44, total 64.
    Loading of 'SAPAPPL2_9' import package: ERROR
    Import Monitor jobs: running 0, waiting 19, completed 0, failed 45, total 64.
    Import Monitor jobs: running 1, waiting 18, completed 0, failed 45, total 64.
    Import Monitor jobs: running 2, waiting 17, completed 0, failed 45, total 64.
    Import Monitor jobs: running 3, waiting 16, completed 0, failed 45, total 64.
    Loading of 'SAPSSEXC_10' import package: ERROR
    Import Monitor jobs: running 2, waiting 16, completed 0, failed 46, total 64.
    Loading of 'SAPAPPL2_3' import package: ERROR
    Import Monitor jobs: running 1, waiting 16, completed 0, failed 47, total 64.
    Loading of 'SAPAPPL0_6' import package: ERROR
    Import Monitor jobs: running 0, waiting 16, completed 0, failed 48, total 64.
    Import Monitor jobs: running 1, waiting 15, completed 0, failed 48, total 64.
    Import Monitor jobs: running 2, waiting 14, completed 0, failed 48, total 64.
    Import Monitor jobs: running 3, waiting 13, completed 0, failed 48, total 64.
    Loading of 'SAPSLEXC' import package: ERROR
    Import Monitor jobs: running 2, waiting 13, completed 0, failed 49, total 64.
    Loading of 'SAPAPPL0_9' import package: ERROR
    Import Monitor jobs: running 1, waiting 13, completed 0, failed 50, total 64.
    Loading of 'SAPAPPL2_11' import package: ERROR
    Import Monitor jobs: running 0, waiting 13, completed 0, failed 51, total 64.
    Import Monitor jobs: running 1, waiting 12, completed 0, failed 51, total 64.
    Import Monitor jobs: running 2, waiting 11, completed 0, failed 51, total 64.
    Import Monitor jobs: running 3, waiting 10, completed 0, failed 51, total 64.
    Loading of 'SAPSPROT' import package: ERROR
    Import Monitor jobs: running 2, waiting 10, completed 0, failed 52, total 64.
    Loading of 'SAPAPPL2_13' import package: ERROR
    Import Monitor jobs: running 1, waiting 10, completed 0, failed 53, total 64.
    Loading of 'SAPAPPL2_12' import package: ERROR
    Import Monitor jobs: running 0, waiting 10, completed 0, failed 54, total 64.
    Import Monitor jobs: running 1, waiting 9, completed 0, failed 54, total 64.
    Import Monitor jobs: running 2, waiting 8, completed 0, failed 54, total 64.
    Import Monitor jobs: running 3, waiting 7, completed 0, failed 54, total 64.
    Loading of 'SAPSLOAD' import package: ERROR
    Import Monitor jobs: running 2, waiting 7, completed 0, failed 55, total 64.
    Loading of 'SAPSDOCU' import package: ERROR
    Import Monitor jobs: running 1, waiting 7, completed 0, failed 56, total 64.
    Loading of 'SAPAPPL1_1' import package: ERROR
    Import Monitor jobs: running 0, waiting 7, completed 0, failed 57, total 64.
    Import Monitor jobs: running 1, waiting 6, completed 0, failed 57, total 64.
    Import Monitor jobs: running 2, waiting 5, completed 0, failed 57, total 64.
    Import Monitor jobs: running 3, waiting 4, completed 0, failed 57, total 64.
    Loading of 'SAPDDIM' import package: ERROR
    Import Monitor jobs: running 2, waiting 4, completed 0, failed 58, total 64.
    Loading of 'SAPUSER' import package: ERROR
    Import Monitor jobs: running 1, waiting 4, completed 0, failed 59, total 64.
    Loading of 'SAPDFACT' import package: ERROR
    Import Monitor jobs: running 0, waiting 4, completed 0, failed 60, total 64.
    Import Monitor jobs: running 1, waiting 3, completed 0, failed 60, total 64.
    Import Monitor jobs: running 2, waiting 2, completed 0, failed 60, total 64.
    Import Monitor jobs: running 3, waiting 1, completed 0, failed 60, total 64.
    Loading of 'SAPDODS' import package: ERROR
    Import Monitor jobs: running 2, waiting 1, completed 0, failed 61, total 64.
    Loading of 'SAPUSER1' import package: ERROR
    Import Monitor jobs: running 1, waiting 1, completed 0, failed 62, total 64.
    Loading of 'SAP0000' import package: ERROR
    Import Monitor jobs: running 0, waiting 1, completed 0, failed 63, total 64.
    ERROR 2009-10-27 10:53:37.125
    CJS-30022  Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
    ERROR 2009-10-27 10:53:37.140
    FCO-00011  The step runMigrationMonitor with step key |NW_Doublestack_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|2|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR ( Last error reported by the step :Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.).
    Thanks.

    i checked the DOKCLU log, pls find the log below:
    D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: START OF LOG: 20091027104307
    D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: sccsid @(#) $Id: //bas/700_REL/src/R3ld/R3load/R3ldmain.c#20 $ SAP
    D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: version R7.00/V1.4 [UNICODE]
    Compiled Aug 23 2009 23:42:38
    D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe -i DOKCLU.cmd -dbcodepage 4103 -k 1gage5M50Dp01eqte1]x3Qa5 -l DOKCLU.log -stop_on_error -loadprocedure fast LOAD
    (DB) INFO: connected to DB
    (GSI) INFO: dbname   = "ATD                                                                                "
    (GSI) INFO: vname    = "DB6                             "
    (GSI) INFO: hostname = "UNKNOWN                                                         "
    (GSI) INFO: sysname  = "Windows NT"
    (GSI) INFO: nodename = "SERVER"
    (GSI) INFO: release  = "5.2"
    (GSI) INFO: version  = "3790 Service Pack 1"
    (GSI) INFO: machine  = "4x AMD64 Level 6 (Mod 23 Step 7)"
    (DB) ERROR: DDL statement failed
    ( DROP TABLE "DOKCLU" )
    dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    (DB) ERROR: DDL statement failed
    ( CREATE TABLE "DOKCLU" ( "ID" SAPDB6CHAR(2) DEFAULT ' ' NOT NULL , "OBJECT" SAPDB6CHAR(60) DEFAULT ' ' NOT NULL , "LANGU" SAPDB6FIXCHAR(1) DEFAULT ' ' NOT NULL , "TYP" SAPDB6FIXCHAR(1) DEFAULT ' ' NOT NULL , "DOKVERSION" SAPDB6FIXCHAR(4) DEFAULT '0000' NOT NULL , "PAGENO" SMALLINT DEFAULT 0 NOT NULL , "TIMESTMP" SAPDB6CHAR(46) DEFAULT ' ' NOT NULL , "PAGELG" SMALLINT DEFAULT 0 NOT NULL , "VARDATA" VARCHAR(3800) FOR BIT DATA  ) IN ATD#ES700D INDEX IN ATD#ES700I LONG IN ATD#ES700D )
    dsql_exec_immediate returned DS_DBOBJECTUNKNOWN
    (DB) INFO: disconnected from DB
    D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: job finished with 1 error(s)
    D:\usr\sap\ATD\SYS\exe\uc\NTAMD64\R3load.exe: END OF LOG: 20091027104307
    Thanks

  • New Development system copy from Production

    Hi All,
    Hope you can help me out here with some ideas.
    We are currently planning to implement a new SAP BW Development system, and for this we would like to make it a 1:1 copy of our current production system. Meaning all from customizing, ABAP, workbench objects etc.
    But what we do not want is all the transaction and master data in infoobject, cubes etc., we are only interested in the structure and objects. Therefore we can rule out "System copy".
    My question is then, is there any other ways to do this when system copy is a no go? I know we can do client copy but then we will not get all the workbench / ABAP programs which we need.
    Any ideas on how to do this?
    Thx. in Advance

    Hi Rasmus,
    But what we do not want is all the transaction and master data in infoobject, cubes etc., we are only interested in the structure and objects. Therefore we can rule out "System copy".
    Options 1: As BI objects are cross client , copying client will not solve your purpose 100%.
                    You can perform system copy and then clean up data in DEV
    Option 2: You can create a new Development and then create TRs for required configuration objects and move to new development system.
    Option 3: Use SLO tools to perform container copy without any data.
    Hope this helps.
    Regards,
    Deepak Kori

  • Migrate SAP from DB2 9.5 to DB2 9.7 using System copy

    Hello,
    We are migrating our SAP systems to new hardware and we are also planning to upgrade our database from DB2 9.5 to DB2 9.7. So my question is can we take a db backup of our current SAP system which is on DB2 9.5 and install the target SAP instance directly on DB2 9.7 during the System copy?
    Or do we need to install the target SAP instance on DB2 9.5 and then upgrade the system to DB2 9.7 after the System copy procedure.
    Please let me know as we need to start the migration at the earliest.
    Thanks
    D

    Hi Deepak,
    Yes, that is possible (but only offline backup). But for the new features like reclaimable tablespace (to lower the high watermark)
    it's better to export/import with systemcopy.
    Also with systemcopy you can use index compression.
    After backup and restore you can have also reclaimable tablespace, but you have to create new tablespaces
    and then work with db6conv and online table move to move one tablespace online to the new one.
    Best regards,
    Joachim

  • 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

  • DB Error during System Copy Import

    Hello,
    We are currently doing a heterogeneous system copy of an internal Solution Manager
    7.01 (running on Linux SLES10 SP2 64Bit) to a new machine (running on
    Linux SLES11 SP1 64Bit). The database we are using on both side is MaxDB.
    During the export phase, nothing went wrong. The pre and post requisites were implemented.
    But during the import phase with sapinst and more especially during the 'import ABAP' step we are facing the following errors.
    __SAPDFACT.log :__
    (IMP) ERROR: DbSlExeModify/DbSlLobPutPiece failed
      rc = 26, table "/BI0/F0SMD_PI2H"
    DbSl Trace: EXECUTE on connection 0, rc=-7055 (POS(59) Column(s) already
    indexed:/BI0/E0CCMARCDH~P)
    ERROR : Execute for create index /BI0/E0CCMARCDH~P on /BI0/E0CCMARCDH
    failed (dbrc=99).
      (SQL error -7055)
      error message returned by DbSl:
    SQL-Statement: CREATE  INDEX "/BI0/E0CCMARCDH~P" ON "/BI0/E0CCMARCDH" (
    "KEY_0CCMARCDHP" , "KEY_0CCMARCDHT" , "KEY_0CCMARCDHU" ,
    "KEY_0CCMARCDH1" , "KEY_0CCMARCDH2" , "KEY_0CCMARCDH3" ,
    "KEY_0CCMARCDH4" , "KEY_0CCMARCDH5" , "KEY_0CCMARCDH6" ,
    "KEY_0CCMARCDH7" , "KEY_0CCMARCDH8" , "KEY_0CCMARCDH9" ,
    "KEY_0CCMARCDHB"  )
    SAPAPPL1.log :
    (DB) ERROR: DDL statement failed
    (DROP INDEX "/TMWFLOW/TRORDHT~1" ON "/TMWFLOW/TRORDHT")
    DbSlExecute: rc = 103
      (SQL error -4011)
      error message returned by DbSl:
    (IMP) INFO: a failed DROP attempt is not necessarily a problem
    DbSl Trace: EXECUTE on connection 0, rc=-7055 (POS(59) Column(s) already
    indexed:/BI0/E0CCMARCDH~P)
    ERROR : Execute for create index /BI0/E0CCMARCDH~P on /BI0/E0CCMARCDH
    failed (dbrc=99).
      (SQL error -7055)
      error message returned by DbSl:
    SQL-Statement: CREATE  INDEX "/BI0/E0CCMARCDH~P" ON "/BI0/E0CCMARCDH" (
    "KEY_0CCMARCDHP" , "KEY_0CCMARCDHT" , "KEY_0CCMARCDHU" ,
    "KEY_0CCMARCDH1" , "KEY_0CCMARCDH2" , "KEY_0CCMARCDH3" ,
    "KEY_0CCMARCDH4" , "KEY_0CCMARCDH5" , "KEY_0CCMARCDH6" ,
    "KEY_0CCMARCDH7" , "KEY_0CCMARCDH8" , "KEY_0CCMARCDH9" ,
    "KEY_0CCMARCDHB"  )
    Before the export we executed the report for the DDL migration, created
    the right *.sql files. We copied those sql files in the right folder
    according to note 771209 and the System Copy guide.
    We also tried to implement note 942540 - System copy fails on SAPDFACT
    import, but we are not able to drop the mentioned tables. We are
    getting 'unknown tables' whereas we see them in DB.
    We would like to avoid restarting the export and import phases from the beggining as there is approximately 80GB to transfer each time and we are not running this on a server but desktop PC.
    Any help would be appreciated.
    Thanks in advance
    Regards,
    Johann

    Hello Andreas
    thank you for your answer. However, the table specified in the Note is not found when I am running the specified request in the correct schema:
    -4004: POS(16) Unknown table name:/MAXDB/INDEXSTATEMENTS SQLSTATE: 42000
    SAP_BW component in Solution Manager 7.01 SPS24 is SAPKW70106. As this BW release is already more recent than the one recommended in the Note, this issue should not be link to an old BW component patch version then.
    In the meantime, I have applied Notes 888210 and 942540. But I cannot drop the tables specified since the user SAPSMJ has no DROPIN privilege and I cannot grant them even when using SUPERDBA user.
    So I think we need to re-run the export as we are running out of options to try continuing the import phase.
    Regarding the use of last R3load release, would you know the path to download it on the marketplace and if I need the last  R3load kernel version (7.3) or only the last patch for 7.01 and knowing that I am using Netweaver 7.01 packages for the copy ? R3load used so far is 7.01/V1.4.
    Thanks and Regards,
    Johann

Maybe you are looking for