Unable to Load Database/Unable to create database.

RoboHelp 6.0 on my PC is suddenly unable to open existing
projects or create new ones. The problem is not in the projects, as
other people can unzip the same set of files and open them with
RoboHelp on their PCs.
The Details:
When attempting to open an existing project (any project
whether in version control or not), I get the message " Open
project was cancelled or the application was unable to load
database for..."
I found the article that says to delete the CPD and XPJ files
and then to use the Edit option to open the HHP file so that
RoboHelp will recreate the two files. When I try that, I get the
message "Unable to create database. Check that the directory is not
read-only." It's
not read-only.
When I attempt to create a new project, the application acts
like it is going to create one, but it just creates a project
folder without the new first topic and then repeats the New Project
Wizard window that prompts for title, etc. It will keep creating
folders and returning to this window in a loop without ever really
creating a project.
RoboSource Control is functioning normally, by the way.
I have uninstalled and reinstalled RH 6 several times, and
have even uninstalled RH 6 and installed to RH 5 just to see if it
could open projects, which it does with no problems. After that
test, I uninstalled RH 5 and reinstalled RH 6, only to encounter
the same problem all over again.
This started happening after I uninstalled other unrelated
software and received a message that some Service Pack 2 files had
been changed and prompting me to insert the Service Pack 2 CD,
which I don't have. This is because our IT department pre-builds
our systems from an image and then distributes job-specific
applications over the network. IT tried repairing Service Pack 2,
but that didn't work. I'd like to uninstall and reinstall Service
Pack 2, but the IT person says it's too risky on a system that was
built from an image.
We would like to find out
which files RoboHelp is looking for when it launches a
project so we can replace those files manually. Does anyone
know what they are or have another suggestion that might fix the
problem?
Otherwise, I am stuck having to allow IT to rebuild my
system. That means reinstalling and reconfiguring everything on it,
just as if I were upgrading to a new PC. This can take a whole work
week. However, I have already spent close to a work week on this
problem, so maybe rebuilding would save time in the long
run.

Problem Resolution = HHA.dll
For anyone who might be interested in the resolution to this
issue, we did rebuild my PC and reinstall all of my software. The
RoboHelp installation "complained" that I did not have HTML Help
Workshop on my system and told me to download version 1.4 from
Microsoft. I did have HTML Help Workshop..it's in my programs list.
(It's not listed in programs on my co-workers' PCs, and they were
not having problems, by the way.) But to make RH happy, I
uninstalled the workshop and tried to install the version from
Microsoft. But a message informed me that I already had a newer
version of the workshop on my system, and I was back where I
started. I could open projects, but there were weird problems.
Selecting Topic Properties was met with an error message, and when
the properties window opened, I could only see whatever template
was assigned (or none if the topic had lost its template), and
there was an extra section for Oracle help.
So I started dinking around in the registry to see if I could
get rid of any traces of the workshop so I could install the
version RH wanted or to find any other clues to my problem. Under
HTMLHelpAuthor, there was a reference to an HHA.dll file located in
C:\WINDOWS\system32...only the file did not exist on my system.
(Remember that my original problem was that some Service Pack 2
files were either modified or missing.) So I did a Google search on
that file name and found out that HTML Help Workshop is included in
newer Windows operating systems, but that people used to have to
get HTML Help Workshop from Microsoft, and that some people had
made the mistake of just putting the HHA.dll file into the
C:WINDOWS\system32 folder without also installing HTML Help
Workshop. At this point it was obvious that I needed the HHA.dll,
so I got it from a co-worker's PC. (Looking at the registry
entries, I can also see that my system was built with a slightly
different version of the operating system than my co-workers have.)
Adding the HHA file to my system solved the problem. All
projects but one were fine; one was still exhibiting the strange
behavior. I fixed it by going back to the RoboHelp 5 version of the
project and re-converting it to RoboHelp 6.
I suspect that if I had known about the HHA.dll file before
we rebuilt the PC, I could have solved the problem without going
through that painful process. That is why I thought I should post
the solution even though it was after the rebuild.

Similar Messages

  • Can I create a non-Unicode database manually via create database segment

    Hi
    As unicode encode use more bytes than 2-bytes encode (for instance, ZHS16GBK), and XE has the limit with 4GB totally. So, can I create a non-Unicode (for instance, ZHS16GBK) database manually via create database segment? or I just could use unicode?
    Thanks.
    Samuel

    Could you load or paste this scripts? Well, the script is (obviously) a shell script, useless on Windows, unless you have some emulator (CygWin, MKS toolkit or similar). The following is the Sql part :
    sqlplus /nolog <<END
    spool xe_createdb.log
    connect sys/oracle as sysdba
    startup nomount pfile=$filedir/init$ORACLE_SID.ora
    whenever sqlerror exit;
    create database
      maxinstances 1
      maxloghistory 2
      maxlogfiles 16
      maxlogmembers 2
      maxdatafiles 30
    datafile '$filedir/system.dbf'
      size 200M reuse autoextend on next 10M maxsize 600M
      extent management local
    sysaux datafile '$filedir/sysaux.dbf'
      size 10M reuse autoextend on next  10M
    default temporary tablespace temp tempfile '$filedir/temp.dbf'
      size 20M reuse autoextend on next  10M maxsize 500M
    undo tablespace undo datafile '$filedir/undots1.dbf'
      size 50M reuse autoextend on next  5M maxsize 500M
    --character set al32utf8
    character set $dbcharset
    national character set al16utf16
    set time_zone='00:00'
    controlfile reuse
    logfile '$filedir/log1.dbf' size 50m reuse
           , '$filedir/log2.dbf' size 50m reuse
           , '$filedir/log3.dbf' size 50m reuse
    user system identified by oracle
    user sys identified by oracle
    -- create the tablespace for users data
    create tablespace users
      datafile '$filedir/users.dbf'
      size 100M reuse autoextend on next 10M maxsize 5G
      extent management local
    -- install data dictionary views:
    @?/rdbms/admin/catalog.sql
    -- run catblock
    @?/rdbms/admin/catblock
    -- run catproc
    @?/rdbms/admin/catproc
    -- run catoctk
    @?/rdbms/admin/catoctk
    -- run pupbld
    connect system/oracle
    @?/sqlplus/admin/pupbld
    @?/sqlplus/admin/help/hlpbld.sql helpus.sql;
    -- run plustrace
    connect sys/oracle as sysdba
    @?/sqlplus/admin/plustrce
    -- Install context
    @?/ctx/admin/catctx oracle SYSAUX TEMP NOLOCK;
    connect CTXSYS/oracle
    @?/ctx/admin/defaults/dr0defin.sql "AMERICAN"
    -- Install XDB
    connect sys/oracle as sysdba
    @?/rdbms/admin/catqm.sql oracle SYSAUX TEMP;
    connect SYS/oracle as SYSDBA
    @?/rdbms/admin/catxdbj.sql;
    connect SYS/oracle as SYSDBA
    @?/rdbms/admin/catxdbdbca.sql 0 8080;
    connect SYS/oracle as SYSDBA
    begin dbms_xdb.setListenerLocalAccess( l_access => TRUE ); end;
    -- Install Spatial Locator
    connect sys/oracle as sysdba
    create user MDSYS identified by MDSYS account lock;
    @?/md/admin/catmdloc.sql
    create spfile='$filedir/spfile.ora' from pfile
    alter user anonymous account unlock
    disconnect
    -- recompile invalid objects
    connect sys/oracle as sysdba
    begin dbms_workload_repository.modify_snapshot_settings(interval => 0); end;
    begin dbms_scheduler.disable('AUTO_SPACE_ADVISOR_JOB', true); end;
    spool off
    exit
    ENDWords prefixed with $ are OS variables, you have to substitute them with your values.

  • If ur database crash u have only export of database how u create database f

    if ur database crash u have only export of database how u create database from starting with help of export give steps

    What is an "export give steps?"
    If ur's database crashes, how is it u's responsibility to restore it?
    Now, if my database crashes, I just restart it in crash recovery mode and not even worry about the backup or export. It is not needed.

  • Unable to access table even after creating Database link

    Hi
    I have created a data base link.It was created properly.
    The Syantax that I have used is follows:
    create database link X_link connect to User1 identified by User1 using 'Other_Database'
    And on running the query:
    select count(*) from table1@X_link
    I am getting the error as follows:
    TNS could not resolve the connect identifier specified... TNS: could not resolve the connect identifier specified.
    Please tell me where is the problem?
    Thanks in Advance

    Your database link does not work because the entry you used does not exist in the tnsnames.ora in the database $ORACLE_HOME.
    Login to the database server, set the environment, and try to tnsping the entry you used for the database link, then fix the tnsnames.ora file (probably in $ORACLE_HOME/network/admin)
    You can test a database link using :-
    select sysdate from dual@link;

  • Unable to load data into any application.database on server.

    I have a rather odd problem that's been vexing my for a few days.
    I am unable to do a data import into any cubes within Essbase, its as if the cube is in read only mode, though everything seems OK. I'm not running any sort of archiving, and to manually check, within essmsh, I did an "alter database end archive". I've tried with our existing and unchanged data load script as well as from within the EAS ( Right-click Data Load ). If I check the processes running on the server ( LINUX server ) the ESSSVR process is the top process eating 100% CPU. I can do outline builds OK.
    From within the application log file, the last few entries are:
    [Wed Apr  3 09:44:58 2013]Local/OP_ACC/Accounts/svc_biserver/Info(1021044)
    Starting to execute query
    [Wed Apr  3 09:44:58 2013]Local/OP_ACC/Accounts/svc_biserver/Info(1021045)
    Finished executing query, and started to fetch records
    [Wed Apr  3 09:44:58 2013]Local/OP_ACC/Accounts/svc_biserver/Info(1021000)
    Connection With SQL Database Server is Established
    [Wed Apr  3 09:44:58 2013]Local/OP_ACC/Accounts/svc_biserver/Info(1003040)
    Parallel dataload enabled: [1] block prepare threads, [1] block write threads.
    [Wed Apr  3 09:45:19 2013]Local/OP_ACC/Accounts/svc_biserver/Info(1021047)
    Finished fetching data
    Nothing has changed on this server for a few weeks so I'm somewhat flummoxed and no other errors show in any other logs ( nohup.out ).
    Essbase 11.1.1.2
    Redhat LINUX_x64 2.6

    Yes, I tried rebooting the whole box, server has 9Gb free space, same story when I load just 1 row via a text file in the EAS, it seems to hang and the ESSSVR process for that cube goes to 100%.
    I've tried a few different cubes, and they all have the same problem, so I suspect its something to do with Essbase itself rather than the specific cube I'm having problems with.
    This is our test server I'm experiencing the problem with and I tried migrating 1 app from UAT back to test which still didnt work.
    Stumped!

  • Unable to move mailbox to newly created database in exchange 2013

    Hi, i created a new database in our existing exchange server 2013 sp1 and i was trying to move my mailbox to the newly created one using the EAC. But the mailbox is not getting moved and i am not receiving any errors. Is there anything else i need to do
    after creating the database.
    Please advise.

    Hello
    lets play again:
    new-moverequest -identity useremailaddress -targetdatabase new database
    after two minute get move req log
    get-moverequest -identity useremailaddress |get-moverequeststatistics -includereport |fl
    or if have got more DC specified one Dc with -domincontroller DCname
    sorry my english

  • CSA MC Install error: Unable to load patch information

    When we try to install CSA MC 5.2.0.263 (and 5.2.0.203) on Windows Server 2003 Ent Ed (or R2) we receive error:
    "Unable to load patch information into the database"
    How to solve the given error?

    Just a couple things to check. If running the CSA agent on the MC make sure its disabled during the upgrade
    You have enough free space in the installation directory

  • Unable to load MTS (AVCHD) file

    I just installed Adobe Premiere Elements 12.
    When I try to imort ( load) a AVCD  (.MTS)  file  from my HD , I receive an error message :
    'unable to open the file ,  missing Codec '.
    Can someone help me how I can import these kind of files ?? ( saved on my harddisk) .
    Thanks

    Hello ,
    The JVC model is possible only available in Europe ??
    I do recording in AVCHD  compression  ( wich is the standard fort his camera ) always with a filename  .MTS
    The recorded frame saize is  1920 x 1080  at 50fps  ( european standard ).
    I have transferred one file (.MTS)  into my C-drive  -  same result !! the programm says that i have a missing codec .
    Apple quicktime  version 7.7 ( latest)  is running …
    On the thubnail in the folder panel  within premiere elements , I see a green screen with some flickering on top of the thubnail.
    Can You help me ??
    Thanks a lot,
    Rgds,
    Mike.
    Van: A.T. Romano [email protected]
    Verzonden: donderdag 7 november 2013 15:41
    Aan: mike devos
    Onderwerp: Unable to load MTS (AVCHD) file
    Re: Unable to load MTS (AVCHD) file
    created by A.T. Romano <http://forums.adobe.com/people/A.T.+Romano>  in Premiere Elements - View the full discussion <http://forums.adobe.com/message/5822968#5822968

  • Problem when creating Database:

    There are two problems, which I faced during creation of database. When creating database with Oracle Database Assistant. One when creating pre tuned database from CD. And second when creating customized database giving options your self.
    Problem # 1:
    When creating pre tuned database from CD. The process of creating Database is 90 % complete and is at step # 3 Initializing Database. It gives error ORA-03113: end-of-file on communication channel.
    I searched following oracle help for this problem.
    ORA-03113: end-of-file on communication channel
    Cause: An unexpected end-of-file was processed on the communication channel. The problem could not be handled by the Net8, two-task software. This message could occur if the shadow two-task process associated with a Net8 connect has terminated abnormally, or if there is a physical failure of the interprocess communication vehicle, that is, the network or server machine went down.
    Action: If this message occurs during a connection attempt, check the setup files for the appropriate Net8 driver and confirm Net8 software is correctly installed on the server. If the message occurs after a connection is well established, and the error is not due to a physical failure, check if a trace file was generated on the server at failure time. Existence of a trace file may suggest an Oracle internal error that requires the assistance of customer support.
    Conclusion:
    What I conceive from this problem and the help available is that, I have to install NET8 again. But I am not sure about the solution, please tell me whether I am rite or not.
    Problem # 2:
    When creating database with custom option. The process of creating Database is 2 % complete and is at step # 2 Creating Database Files. It gives error ORA-12571: TNS:packet writer failure.
    I searched following oracle help for this problem.
    ORA-12571: TNS:packet writer failure
    Cause: An error occurred during a data send.
    Action: Not normally visible to the user. For further details, turn on tracing and re-execute the operation. If error persists, contact Worldwide Customer Support.
    Conclusion:
    What I conceive from this problem and the help available is that, I have to install NET8 again. But I am not sure about the solution, please tell me whether I am rite or not.

    user563502 wrote:
    I am working on Solaris 8. What is Alert_SID.log? where can I find it?
    ThanksFor the responsible of the upgrade of Oracle database, not even know what Alert log is?
    to be honest with you, this is not your work.

  • Problem when creating Database with Database, OS and hardware Configuraiton

    Problem when creating Database:
    There are two problems, which I faced during creation of database. When creating database with Oracle Database Assistant. One when creating pre tuned database from CD. And second when creating customized database giving options your self.
    Problem # 1:
    When creating pre tuned database from CD. The process of creating Database is 90 % complete and is at step # 3 Initializing Database. It gives error ORA-03113: end-of-file on communication channel.
    I searched following oracle help for this problem.
    ORA-03113: end-of-file on communication channel
    Cause: An unexpected end-of-file was processed on the communication channel. The problem could not be handled by the Net8, two-task software. This message could occur if the shadow two-task process associated with a Net8 connect has terminated abnormally, or if there is a physical failure of the interprocess communication vehicle, that is, the network or server machine went down.
    Action: If this message occurs during a connection attempt, check the setup files for the appropriate Net8 driver and confirm Net8 software is correctly installed on the server. If the message occurs after a connection is well established, and the error is not due to a physical failure, check if a trace file was generated on the server at failure time. Existence of a trace file may suggest an Oracle internal error that requires the assistance of customer support.
    Conclusion:
    What I conceive from this problem and the help available is that, I have to install NET8 again. But I am not sure about the solution, please tell me whether I am rite or not.
    Problem # 2:
    When creating database with custom option. The process of creating Database is 2 % complete and is at step # 2 Creating Database Files. It gives error ORA-12571: TNS:packet writer failure.
    I searched following oracle help for this problem.
    ORA-12571: TNS:packet writer failure
    Cause: An error occurred during a data send.
    Action: Not normally visible to the user. For further details, turn on tracing and re-execute the operation. If error persists, contact Worldwide Customer Support.
    Conclusion:
    What I conceive from this problem and the help available is that, I have to install NET8 again. But I am not sure about the solution, please tell me whether I am rite or not.
    Software & Hardware Configuration are as follow:
    Software:
    Database
    Oracle 8.1.7.0.0 (Oracle8i)
    Operating System
    Microsoft Windows 2000
    5.00.2195
    Service Pack 2
    Hardware:
    x86 Family 6 Model 8 stepping
    10
    AT/AT COMPITABLE
    260,400 KB RAM

    user563502 wrote:
    I am working on Solaris 8. What is Alert_SID.log? where can I find it?
    ThanksFor the responsible of the upgrade of Oracle database, not even know what Alert log is?
    to be honest with you, this is not your work.

  • Problem when creating Database (Database, OS and hardware Configuraiton)

    Problem when creating Database:
    There are two problems, which I faced during creation of database. When creating database with Oracle Database Assistant. One when creating pre tuned database from CD. And second when creating customized database giving options your self.
    Problem # 1:
    When creating pre tuned database from CD. The process of creating Database is 90 % complete and is at step # 3 Initializing Database. It gives error ORA-03113: end-of-file on communication channel.
    I searched following oracle help for this problem.
    ORA-03113: end-of-file on communication channel
    Cause: An unexpected end-of-file was processed on the communication channel. The problem could not be handled by the Net8, two-task software. This message could occur if the shadow two-task process associated with a Net8 connect has terminated abnormally, or if there is a physical failure of the interprocess communication vehicle, that is, the network or server machine went down.
    Action: If this message occurs during a connection attempt, check the setup files for the appropriate Net8 driver and confirm Net8 software is correctly installed on the server. If the message occurs after a connection is well established, and the error is not due to a physical failure, check if a trace file was generated on the server at failure time. Existence of a trace file may suggest an Oracle internal error that requires the assistance of customer support.
    Conclusion:
    What I conceive from this problem and the help available is that, I have to install NET8 again. But I am not sure about the solution, please tell me whether I am rite or not.
    Problem # 2:
    When creating database with custom option. The process of creating Database is 2 % complete and is at step # 2 Creating Database Files. It gives error ORA-12571: TNS:packet writer failure.
    I searched following oracle help for this problem.
    ORA-12571: TNS:packet writer failure
    Cause: An error occurred during a data send.
    Action: Not normally visible to the user. For further details, turn on tracing and re-execute the operation. If error persists, contact Worldwide Customer Support.
    Conclusion:
    What I conceive from this problem and the help available is that, I have to install NET8 again. But I am not sure about the solution, please tell me whether I am rite or not.
    Software & Hardware Configuration are as follow:
    Software:
    Database
    Oracle 8.1.7.0.0 (Oracle8i)
    Operating System
    Microsoft Windows 2000
    5.00.2195
    Service Pack 2
    Hardware:
    x86 Family 6 Model 8 stepping
    10
    AT/AT COMPITABLE
    260,400 KB RAM

    user563502 wrote:
    I am working on Solaris 8. What is Alert_SID.log? where can I find it?
    ThanksFor the responsible of the upgrade of Oracle database, not even know what Alert log is?
    to be honest with you, this is not your work.

  • How to create database link between oracle and SQL Server

    Hello Everyone,
    Here i have Oracle Database 9i and SQL Server 2005 databases.
    I have some tables in sql server db and i want to access from Oracle.
    How to create a database link between these two servers
    Thanks,

    Thanks for Everyone,
    I was struggle with this almost 10 days....
    I created Database link from Oracle to SQL Server
    Now it is fine.........
    Here i am giving my servers configuration and proceedure how i created the db link...@
    Using Generic Connectivity (HSODBC) we can create db link between Oracle and SQL server.
    Machine (1)
    DB Version : Oracle 9.2.0.7.0
    Operating System : HP-UX Itanuim 64 11.23
    IP : 192.168.0.31
    Host : abcdbt
    Machine (2)
    Version : SQL Server 2005
    Operating System : Windows server 2003 x86
    IP : 192.168.0.175
    Host : SQLDEV1
    User/PW : sa/abc@123! (Connect to database)
    Database : SQLTEST (exsisting)
    Table : T (“ T “ is the table existing in SQLTEST database with 10 rows)
    Prerequisites in Machine (2):
    a)     Oracle 10g software
    b)     User account to access SQL Server database (sa/abc@123!)
    c)     Existing SQL Server Database (SQLTEST)
    d) Tables (testing purpose) (T)
    Steps:
    1)     Install Oracle 10.2.0.1 (Only SW,No need of database) *(Machine 2)*
    2)     Create a DSN where your windows Oracle 10g SW resides *(Machine 2)*
    Control panel >> Administrative Tools >> Data Source (ODBC) >> System DSN ADD
    You can follow this link also.....
    http://www.databasejournal.com/features/oracle/article.php/3442661/Making-a-Connection-from-Oracle-to-SQL-Server.htm
    I created DSN as
    DSN name : SQLTEST
    User : SA/abc@123! (Existing user account)
    Host : 192.168.0.175 (machine 2)
    Already I have 1 database in SQL Server with the name SQLTEST
    You can create DSN with different name also (not same as db name also)
    3)     Create a hsodbc init file in $ORACLE_HOME\hs\admin *(Machine 2)*
    Create init<DSN NAME> file
    Ex: initSQLTEST
    Copy inithsodbc to initSQLTEST
    And edit
    initSQLTEST file
    HS_FDS_CONNECT_INFO = SQLTEST    <DSN NAME>*
    HS_FDS_TRACE_LEVEL = OFF*
    save the file....@
    4)     Configure Listener.ora *(Machine 2)*
    LISTENER_NEW =
    (DESCRIPTION_LIST =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.0.175)(PORT = 1525))
    SID_LIST_LISTENER_NEW =
    (SID_LIST =
    (SID_DESC =
    (SID_NAME = SQLTEST) *+< Here SQLTEST is DSN NAME >+*
    (ORACLE_HOME = G:\oracle 10g\oracle\product\10.2.0\db_1)
    (PROGRAM = hsodbc))
    (SID_DESC =
    (SID_NAME = PLSExtProc)
    (ORACLE_HOME = G:\oracle 10g\oracle\product\10.2.0\db_1)
    (PROGRAM = extproc) )
    :> lsnrctl start LISTENER_NEW
    5)     Configure tnsname.ora *(Machine 2)*
    SQLTEST11 =
    (DESCRIPTION =
    (ADDRESS_LIST =
    (ADDRESS = (PROTOCOL = TCP)(HOST = 192.168.0.175)(PORT = 1525))
    (CONNECT_DATA =
    (SERVER = DEDICATED)
    (SERVICE_NAME = SQLTEST))
    (HS=OK)
    :> tnsping SQLTEST11
    If No errors then conti….
    6)     Configure a file *(Machine 1)*
    Cd $TNS_ADMIN ($ORACLE_HOME/network/admin)
    Create a file
    $ vi TEST_abcdbt_ifile.ora
    something=
    (DESCRIPTION=
    (ADDRESS=(PROTOCOL=tcp)(HOST =192.168.0.175) (PORT=1525))
    (CONNECT_DATA=
    (SID=SQLTEST))
    (HS=OK)
    $ tnsping something
    $ sqlplus system/manager
    Your connected to Oracle database *(machine 1)*
    create database link xyz connect to “sa” identified by “abc@123!” using ‘SOMETHING’;
    select * from t@xyz;10 rows selected.
    Thanks,
    Edited by: ram5424 on Feb 10, 2010 7:24 PM

  • I can't create Database Instance

    when I use Oracle Database Assistance for create database.
    It display error ' DIM-00019: Create Service error.
    O/S-error:(OS 1388)
    I don't know this error
    I hope sombody to help me
    Thank.

    Are you using Oracle 10g for windows?, then it looks you've hit bug 3537738. Version 10.1.0.2 contains the fix.

  • 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

  • SWPM - System Copy - Assertion Failed Unable to load database

    Hello again,
    (already the next question form me, sorry for this
    I am executing a sysetm copy (DB-refresh) on ASE using SWPM.
    However, in "Configure Components" step I get the error: Assertion failed. Unable to load database <SID of Target Sysetm>.
    Where else can I check for errors?
    I think it is still something on which I already worked (with other thread).
    In sapinst_dev.log I found this
    TRACE      2015-03-25 11:05:00.320
    SAPInst calls the LogInquirer. The output of the LogInquirer can be found in file sapinst_loginquirer.log.
    TRACE      2015-03-25 11:05:06.122 [iaxxgenimp.cpp:638]
                CGuiEngineImp::showMessageBox()
    <html> <head> </head> <body> <p> An error occurred while processing option <i>SAP Enhancement Package 1 for SAP N
    etWeaver 7.3 > SAP ASE > System Copy > Target System > Standard System > Based on AS ABAP > Database Refresh or M
    ove( Last error reported by the step: Assertion failed: Unable to load database <SID>.)</i>. You can now: </p> <ul>
    <li> Choose <i>Retry</i><br>to repeat the current step. </li> <li> Choose <i>Log Files</i><br>to get more inform
    ation about the error. </li> <li> Stop the option and continue later. </li> </ul> <p> Log files are written to /t
    mp/sapinst_instdir/NW731/SYB/COPY/SYSTEM/STD/AS-ABAP/REF. </p> </body></html>
    TRACE      2015-03-25 11:05:06.124 [iaxxgenimp.cpp:1031]
               CGuiEngineImp::acceptAnswerForBlockingRequest
    Waiting for an answer from GUI
    In sapinst.log I found this:
    ERROR 2015-03-25 11:04:59.573
    FCO-00011  The step syb_step_setup_preload with step key |NW_ABAP_DB_DBRefresh|ind|ind|ind|ind|0|0|NW_ABAP_DB|ind
    |ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_CreateDB|ind|ind|ind|ind|createdb|0|NW_S
    YB_DB|ind|ind|ind|ind|SYB_DB_CONTEXT|0|syb_step_setup_preload was executed with status ERROR ( Last error reporte
    d by the step: Assertion failed: Unable to load database <SID>.).
    INFO 2015-03-25 11:04:59.772
    Creating file /tmp/sapinst_instdir/NW731/SYB/COPY/SYSTEM/STD/AS-ABAP/REF/__instana_tmp.xml.
    INFO 2015-03-25 11:05:00.307
    Removed file /tmp/sapinst_instdir/NW731/SYB/COPY/SYSTEM/STD/AS-ABAP/REF/instslana.xml.
    INFO 2015-03-25 11:05:00.308
    Creating file /tmp/sapinst_instdir/NW731/SYB/COPY/SYSTEM/STD/AS-ABAP/REF/instslana.xml.

    Hello Kiran,
    I did a few tests again yesterday, and it was really a stupid mistake from myside.
    The error message did mean, that there wasn't enough space.
    It isn't the authority issue, it was a leak of space.
    FYI, the complete DB-Size of Source System is required - NOT JUST RESERVED SPACE!!!
    Thx for help and sorry for stealing your time :O

Maybe you are looking for