System copy same sid

Dear all
This is the possible for the same *sid* for the Quality and production server .
any problem if taken lisence from the same  SID. From SAP
thanks
with regards
venkat

Hi Venkat, there's a database procedure to make System Copies.
You'll find it at http://service.sap.com/instguides (SAP Netweaver -> SAP Netweaver 7.0 -> Installation -> System Copy for SAP Systems)
If you have any other question, please post it here.
Regards,
Darwin Castillo
SAP Netweaver System Administrator
Santo Domingo, Dominican Republic

Similar Messages

  • Adding systems with same SID in SMSY - solution manager

    Dear All,
    We are having systems with same SID's which  belongs to different landscape created for various customers.
    Currently We are having only one solution manager.
    I consider this example for explanation.
    Customer 1 : DEV --> QAS --> PRD ( SID's)
    customer 2 :  DEV --> ACC --> PRD  ( SID's)
    I would like to add  these 6 systems in a solution manager. For Customer 1 , I have included the systems in SMSY . But when i tries to add DEV, PRD for customer 2 , it fails  since this SID's are already present.
    Is there any other way to include by giving the different SID's DE2 but with correct IP and host Or we need to have one more solution manager ? Please anyone suggest me on this
    Thanks
    Raj

    Dear Juan ,
       We can add systems with same SID in smsy. I have attached the way in which i have done. This may help others. Thank you all for your suggestion
    Only use more than three characters if your landscape contains multiple systems with the same system ID (if you have a mirrored backup system that has the same ID as the original system, for example).
    If multiple systems in your landscape have the same system ID, choose as system name the system ID with a suffix of up to 5 characters (a sequential number, for example) to create a unique system name.
    The system accepts a system name of more than 3 characters if you choose Enter to confirm.
    Thanks
    Raj

  • Create a Connection on TREX for 2 systems with same SID

    Hello world,
    Here is my case,
    We have a PRO systems With SID=PRO On Host= production , and a Sandbox system with also SID=PRO On Host=SANDBOX
    now i need to create a connection in TREX in parallel so when i add the 2nd one it just edits the 1st one that i have already made
    So is it possible to create 2 connection of same SID but diffrent Hosts In parallel?
    If Yes how ?
    Thanks In Advance...
    Ahmed Salam

    Hi Ahmed,
    it could be possible from the TREX perspective , however such configuration isn't supported . The reason for this is that the SAP applications create indexes using the ABAP system ID and client as a part of the index names (f.e. esh:e10002~e10002~acc_sid~sid). As it's not possible to create an index with the same name 2nd time, you will not be able to use the TREX instance with two systems with same SID.
    Best regards,
    Mikhail

  • SID Problem : could not register two ABAP systems with same SID

    Dear Expert:
    We have to register two ABAP systems on different host to SLD, and these two systems have same SID.
    We use rz70 to do this,  but we found the lastest registration will overwrite the previous registration,
    that
    means we could register them both in the same SLD. (we checked this in Technical system area).
    How could we do this?  It makes us crazy........
    Thanks very much
    Ray

    Dear Stefan,
    Thanks so much for your anwser.
    But the dilemma is in one SLD we achieved this, but it is only for one case and we could
    not apply this for other systems.
    This is the snapshot in our SLD for techical system:
    Name                                        Host                             Version                                     Last Update
    D01   on eisdq01                     eisdq01                         700                                           2010/12/06 12:45
    D01   on eisdv01                     eisdv01                         640                                           2010/12/06  11:40
    We don't know if this is the illusion that SLD could do this?  But for other systems, e.g two Q systems
    the lastest registration will overwrite the previsou one.
    Thanks very much.
    Welcome suggestions from very guru.
    Ray

  • Java Add-in System Copy - same Java Support Package levels ?

    Hi,
    I'm looking at performing a standard SAP Netweaver 04 SAP Web Application Server system "refresh" procedure. I plan to copy the production system ( SAP WAS 640 ABAP+Java addin )to an already installed QA system that was installed originally exactly the same as Prod. Both have the same components installed and the ABAP stack Support package levels are identical. What I've found is that the Java Add-in Support package levels vary. Is it possible to perform the system copy "refresh" if the Java components differ. ( Prod J2EE is 640 SP13, QA is SP14 and Adobe & ESS/MSS components differ ).
    I've looked through the system copy guides and the NW04 SR1 system copy OSS note 785848, but can't find anything about this situation.
    Hopefully someone else out there can tell me if it's possible, without first patching Production to the same levels as the QA system being overwritten.
    Regards,
    Brian.

    Hello,
    u can do that w/o applying the patch ..but after doing system copy u have latest SP13 as of u r PRD server instead of SP14 in QA....if required then u can apply it again in QA....SP14.
    So if u not got my point then tell me...
    thanks..
    reward points..

  • Is it possible to install two SAP system with same SID but different instance numbers on one host?

    Is it possible to install two SAP system with same system ID (SID) but different instance numbers on one host?
    If yes, then how?
    If no, then why?
    Thanks in advance.
    Regards,
    Sarim

    Is it possible to install two SAP system with same system ID (SID) but different instance numbers on one host?
    Yes, it is possible. If one is CI (PAS) and the second one is an AS (AAS). In this case there will be only one database.
    If you are talking about two separate SAP systems with separate databases (Eg: A BI and an ECC) with the same SID then the problem will be with the database (Eg: Oracle)
    The database will be installed under /oracle/SID/112_64 (ORACLE_HOME) unless one database is running on 10 G and in that case the ORACLE_HOME will be /oracle/SID/102_64
    The next issue will be with the SAP file systems like /sapmnt/SID
    The most important problem will be with the switch to the sidadm and orasid users and the conflicts there. If there is a need to stop one of the SAP systems and if you do a switch to sidadm and issue a stopsap command which system will be stopped ?
    These are few of the many problems I can think of.
    So if we are talking about two separate systems with their own databases I would rule out the possibility of having two systems with the same SID.
    Regards
    RB

  • What issues we may face in installing a new Prod portal with same SID as existing one

    Hello All -
    We found some vbs script files in the host of EP Prod system. On confirmation from SAP we deleted those files without any harm to our prod EP system. But customer is still concerned about the security of the system and wanted us build the new EP prod system with same SID.
    We approached SAP and they suggested to install a new EP system and do customization rather than performing system copy from existing prod EP system because that may still bring those security threat changes to new EP prod system. (we ll decommission the old EP if everything works fine in new EP)
    Now I would like to list all the issues we may face in building a new EP system with same SID as that of already existing one and then doing entire customization again in new EP from Basis team point of view. The following are very few i could think of. Could you please add some other concerns you could think of.
    1) Keeping in mind that this EP system is in use for more than 6 years, some of the customization could have been done on lower versions. So could those changes be again exported from Dev and imported into new version of EP we are building now ?
    2) Can't add two hosts with same name in DNS Server
    3) Can't add two systems with same SID in Solution Manager for calculation of SPS to upgrade new EP

    You would have to run ipsinstall and install the new gateway. Make sure to follow the installation instruction for installing a gateway.
    After you install the gateway you follow the steps in the link you posted to let the server know there is a new gateway.
    Then make sure to restart the gateway and server.
    HTH ..

  • Requesting license for two different ssystem with same SID

    Hello,
    Is it possible to request 2 license for two systems with same SID. The systems are on different machines and their HW key are different but both have same SID. While requesting license, will it permit to create 2 different license with SAME SID.
    Regards
    Deb

    Hi Anil,
    The one for which the license is already requested is the main development portal with SID EP2. I have installed one local version of SAP EP with the same SID EP2. Now we need a license for the second system.
    If we change the HW key of the original license which is already applied in the main development portal under SMP and apply for a new license for the new local version, can it have any future implications, if any.
    What is the best way to deal with the situation. Is there a full proof way to change the SID of the EP system, which I can try in the local EP system.
    Regards
    Deb

  • 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

  • Same SID for QA & Prd systems - pros and cons?

    We have the foll systems:
    1. Enterprise Portal 7.0
    2. NWDI 7.0
    3. NW 7.0 (with XECO - Ecommerce)
    4. TREX 7.1
    5. Content Server 6.40
    6. ECC 6.0
    Currently the QA and Prd systems have the same SID and system/instance no, although they are on different hosts.
    We would like to know what are the long term pros and cons for keeping the QA and Prd SIDs the same for all systems.
    We are already making a list, so thought we might as well get more inputs from the community too.
    We already have this arrangement for the past 3 months and have not faced any major issues.
    A couple of cons though:
    1. Cannot use solman as it cannot distinguish between the diff servers with same SID
    2. ABAP transports from QA to Prd have to be manually done (cannot use STMS)
    Thanks
    Prasad

    Hi Manoj,
    Changing the SID of java systems is a very tedious procedure. Hom sys copy is just a part of the SID change...there are a whole lot of configs to be done after that...the task is eq to a new setup of systems
    For once, the efforts put in are huge..you can see there are 5 systems..besides, it will involve coordination from all teams - basis, development, functional, project management.
    Here are a few advantages that we know of:
    1. No efforts reqd to change back to original SID
    2. During disaster recovery, we just have to restore the production database on QA and change the hostname, whereas its not so in case of having diff SIDs
    3. For end-users this will be transparent because they will be using the hostname in the URL which is anyways different
    We have the same SIDs for the past 3 months and have not seen major issues, but we also would like to know from the long term perspective if there are any risks that we have not foreseen...hence we seek help from the community.
    Hope its clear now
    Thanks for your response
    Prasad

  • The Java load in database SID / hostname has not been configured yet. You cannot run an installation from the System Copy folder with this load

    Dear Gurus,
    We are facing the below issue when performing a homogeneous system copy of NW 7.0 system using backup/restore method for DB6 system.
    The Java load in database <SID>/<hostname> has not been configured yet. You cannot run an installation from the System Copy folder with this load.
    We went through the SAP Note http://service.sap.com/sap/support/notes/2049842, and followed the same but no luck.
    We updated the Kernel to the latest, but still no luck.
    Request for your quick help as we have to complete it by EOD today.
    Thanks a lot in advance.
    Best Regards,
    Anuj

    Hello Ashutosh ,
    Thanks for your reply.
    We have gone followed the below sequence:
    SCS Installation
    Database Instance Installation using backup/restore method
    CI installation. -> getting error, when we provide the Java Components DVD.
    Best Regards,
    Anuj

  • System copy of a DEV system on the same server

    Hi experts!
    In our company, we have a 2-systems landscape, DEV and PRD, and we are working on the system together with another organization of the same company. Now, they want me to "split" the systems, one for each organization, making a copy of the systems. In other words, they want to completely split the systems, running on the same server, development server will have 2 systems, DEV and DEV' and so on in production server.
    The doubt is in developments, as I don't know how to face the CTS and TMS setup to provide 2 different development environments, without losing the actual change requests for both systems. As you know, I have to change the SID, because the copy will be in the same server, so what happends with change requests?? Do I have to make a copy of DIR_TRANS and set up a new DIR_TRANS for the new system???
    Thank you in advance!
    Fran.

    Hi William,
    I guess I did not explain it properly.
    Now we have:
    1. System DEV in DEV server.
    2. System PRD in PRD server.
    Transport later ZDEV from DEV to PRD.
    And we will do:
    1. Homogeneous system copy from DEV to DEV' in DEV server, so we will have DEV and DEV' on the same server.
    2. Homogeneous system copy from PRD to PRD' in PRD server, so we will have PRD and PRD' on the same server.
    Sizing is good, servers are very powerful.
    The doubt is configuring the TMS, as we will have two different development environments on the same server. How do I have to set up the TMS properly???
    Thanks!!

  • System copy: RZ21 MTE has source SID and not the target SID

    An system copy of PRD to QAS environment has been performed.
    Since then receive the following message in the CCMS Monitor sets (trx RZ20):
    Unable to determine the name of MTE class from <SID>\Background\...\SAP_SRT_COLLECTOR_FOR_MONITORIN or the message "Failed to determine MTE information for system QAS"
    Checked and in the transaction RZ21 the MTE class is pointing to the PRD system and not to the QAS system:
    RZ21 -> MTE-specific properties
    Monitoring: Properties Assigned to MTEs
    RZ21 -> Methods assigned to specific MTEs
    Monitoring: Properties and Methods
    Unable to determine the name of MTE class from PRD\Background\...\SAP_SRT_COLLECTOR_FOR_MONITORIN
    I would expect here the value "QAS\Background\...\SAP_SRT_COLLECTOR_FOR_MONITORIN".
    How can I adjust the MTE to check the QAS instead of the source system PRD ?

    Received following answer from SAP:
    we can find out the follow errors from the dev_disp developer trace file you attached.
    ERROR => e=13 semop(1048668,(0,-1,4096),1)
    (13: Permission denied) [semux.c 1196]
    ERROR => CCMS: AlCreateAttachShm_AS : lock semaphore return 1
    [alxxappl.c 665]
    ERROR => CCMS: sAlInit: could not create/attach shared memory key 13(rtc = 1) [alxx.c 1187]
    ERROR => AlDpAdmInit: sAlInit rtc = 1 [alxx.c 514]
    ERROR => DpLoopInit: AlDpAdmInit [dpxxdisp.c 2033]
    The shared memory area 13 is the one that is responsible for the alert area.
    An error within that area could cause the problem that you are facing when opening monitoring trees.
    If we look at your OS, we can see that the semaphore for this area is currently being held by the root user:
    [1]ipcs | grep 1048668
    s 1048668 0x00004e46 ra-r root system
    You need to delete this area with root user using ipcrm and restart the instace or to reboot the OS and start the instance once again.
    Performed these actions and the issue was solved.

  • How to change the SID during system copy

    This blog /people/johannes.heinrich/blog/2006/07/07/new-features-in-db2-udb-v9--part-3 (i.e.  the "new feature of V9" in this group) only
    talk about the system copy without changing the SID.
    In reality, we often want to change the SID during the system copy. Can we modify the script mentioned in above blog
    to make SID change possible?
    Thanks!

    Hi Christy,
    if you´re using export/import which is prefered you can change the sid during the parameter setting for export and import. You´ll be asked by the old sid and the new sid. For the tablespace names it is not so important because db2 is using tablespace id not the name for the internal administration.
    Regards
    Olaf

  • Two portals (same SID), one R/3 System - changing portal client number?

    We have one R/3 system but two portals.  One is EP6, the other is EP7 and is due to replace EP6.  On installation of version 7.0 we had to keep the SID the same on both portals.
    Now we are having trouble with SSO into R/3 as the ACL in STRUSTSSO2 will only accept one unique SID with client number of 000.  However it does seem to accept the same SID but different client number.
    My question is, is there a way to change one portal generating the verify.der certificate using something other than default 000 client number?
    Is this messy?
    thanks.
    SiB

    Hi Simon,
    > is there a way to change one portal generating the verify.der certificate using
    > something other than default 000 client number
    > Is this messy?
    There is a way and it is absolutely not messy but the supported way; you just have to set the UME property "login.ticket_client" to some different value than "000" on the portal server in question (and of course you have to use this value on the ACL in the SSO target system).
    Also see https://www.sdn.sap.com/irj/sdn/wiki?path=/display/ep/singleSign-Onand+Cookies& -- checklist number 3 and http://help.sap.com/saphelp_nw04/helpdata/en/e2/f71940d4558f5ce10000000a155106/frameset.htm
    I have just done this on my actual project, it's quite straight forward. Remember to restart the portal WAS after changing the value!
    Hope it helps
    Detlev

Maybe you are looking for