Trace application activity in Database side
Hi all
We are using Oracle database 11g (Release 11.1.0.6.0 - 64bit Production) for database and a billing system for client application. Every end of month we are running bill calculation from the front end of our billing system.
The thing i want to do is to know or to get step by step each transaction executed by the Billing application when we launch the bill calculation and bill generation task from the application.
Someone does knows how to proceed on that.
I want to know thwe tables and procedures or function used by the Bill system engine for tuning purpose.
The Os is Linux red hat 5.
Thank you.
Lucienot.
Use TRACE/TKPROF (with wait events) to trace the session that runs the bill calculation.
You might need some help from your DBA.
See:
http://www.oracle-base.com/articles/10g/sql-trace-10046-trcsess-and-tkprof-10g.php
http://docs.oracle.com/cd/E11882_01/server.112/e16638/sqltrace.htm#PFGRF01010
http://docs.oracle.com/cd/E11882_01/server.112/e16638/sqltrace.htm#PFGRF01020
Similar Messages
-
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 -
"error occurred setting the server application active"
Hi All,
I found following error when I save outline in ASO application. It seems that the application cannot be started correctly. Other applications (BSO/ASO) are running correctly.
"error occurred setting the server application active"try this:
Issue can be from both server and application side:
1)Addition of SERVERTHREADS with a proper value. When any database operation is requested then monitor the number of process, memory etc. Idea is to identify which process is trying to use max resource on server level.
2) Also, if possible try and increase the ulimit setting to "unlimited".
3) Verify NETDELAY and NETRETRYCOUNT -- Guess you have checked this so values should be fine here.
4) If the environment is windows then:
a)Open the Registry
b)Navigate to Local Machine\System\CurrentControlSet\Services\TCPIP\Parameters
c)Add new DWORD Value named TcpTimedWaitDelay, right click and select Modify. Select decimal radio button, type in 30. (The default value of this parameter is 2 minutes. This is how long it will take for a TCP/IP port that was used by the network for a connection to be released and made available again. 30 sec is the minimum allowed by Microsoft)
d)Add new DWORD Value named MaxUserPort, right click and select Modify. Select decimal radio button, type in 65534. (The default value is 5000. This determines the highest port number TCP can assign when an application requests an available user port from the system).
e)Add new DWORD Value named MaxFreeTcbs, right click and select Modify. Select decimal radio button, type in 6250. (The default value is 2000. This determines the number of TCP control blocks (TCBs) the system creates to support active connections. Because each connection requires a control block, this value determines how many active connections TCP can support simultaneously. If all control blocks are used and more connection requests arrive, TCP can prematurely release connections in the TIME_WAIT state in order to free a control block for a new connection).
f) Reboot the server.
5) On application side, look at the cache settings, If they are very high then try lowering them and check.
Cheers!!
HA:-)
Edited by: user9513506 on Sep 2, 2008 5:03 AM -
Sort results on app or database side?
I'd like to think that this is a bit trickier than it might first appear. We have some queries that use ORDER BY, and our database guy is telling us to take them out and do them on the web app side to cut down on Oracle 10g's use of the TEMP table. Here's an example of a frequently run query that populates a quick access select box of their address book entries:
SELECT ReceiverID FROM ADDRESSBOOK WHERE AccountNbr = ? ORDER BY UPPER(ReceiverID)We realized that ORDER BY is probably redundant there since the pair key consists of the AccountNbr and ReceiverID, so since it'll use the index they'll come across already sorted. However, when you go searching, you have queries like this, and even more complicated ones as well:
SELECT ReceiverID, CompanyName FROM ADDRESSBOOK WHERE AccountNbr = ? AND UPPER(CompanyName) LIKE UPPER(?) ORDER BY UPPER(CompanyName)In that case, we need to sort, either in the database or on the application side. Typically, the results per account number are around 200 or less, but sometimes it's in the thousands. I've always thought you're supposed to make the database do stuff like this, but if the database is having to go out to disk to use the TEMP table, then maybe in this case it could be better to sort the ResultSet in Java...I was happy to find out that String already has a Comparator for that, so you can write:
Collections.sort(myList, String.CASE_INSENSITIVE_ORDER)However, on the main address book page, they see about five fields of each entry, and they can sort by any of the five fields. So, say the field they want to sort by is CompanyName. Then I'll have to put all the CompanyNames into a List and also into a HashMap where they're a key to the rest of the fields, and then sort the List and pull the CompanyNames out one by one to get the rest of the fields whose info needs to go on the same line on the webpage. In other words, this seems to be the reason for using ORDER BY on the database side in the first place, so please correct me if I'm wrong...You're not wrong. Databases are designed and optimized to do exactly what you're doing; a dba that tells you otherwise would be suspect in my opinion.
-
Unable to find trace file for a particular sid
Hi all,
I have a oracle 9.2.0.6 on solaris platform.I have to use tkrpof for PT for a particular sid.But when i checked out the trace file for that particular sid, i am not able to find out the same.....
SQL> select c.value || '\' || lower(d.value) || '_ora_' || to_char(a.spid, 'fm0
0000') || '.trc' "TRACE FILE"
2 from v$process a, v$session b, v$parameter c, v$parameter d where a.addr =
b.paddr
3 and b.audsid = userenv('sessionid') and c.name = 'user_dump_dest'
4 and d.name = 'db_name';
TRACE FILE
/arch/dump/udump\icai_ora_02464.trc-rw-r----- 1 oracle dba 2526 Nov 9 04:27 icai12_ora_1314.trc
-rw-r----- 1 oracle dba 2528 Nov 9 04:41 icai12_ora_1541.trc
-rw-r----- 1 oracle dba 689 Nov 9 14:26 icai11_ora_14071.trc
-rw-r----- 1 oracle dba 6414 Nov 9 23:56 icai12_ora_456.trc
-rw-r----- 1 oracle dba 1427 Nov 10 12:02 icai11_ora_1867.trc
-rw-r----- 1 oracle dba 613 Nov 10 12:02 icai12_ora_292.trc
-rw-r----- 1 oracle dba 678 Nov 10 12:07 icai11_ora_2356.trc
-rw-r----- 1 oracle dba 613 Nov 10 12:12 icai12_ora_490.trc
-rw-r----- 1 oracle dba 626 Nov 10 12:12 icai11_ora_2275.trc
-rw-r----- 1 oracle dba 613 Nov 10 12:12 icai12_ora_505.trc
-rw-r----- 1 oracle dba 626 Nov 10 12:15 icai11_ora_2430.trc
-rw-r----- 1 oracle dba 613 Nov 10 12:15 icai12_ora_286.trc
-rw-r----- 1 oracle dba 625 Nov 10 12:42 icai11_ora_2378.trc
-rw-r----- 1 oracle dba 625 Nov 10 12:45 icai11_ora_2549.trc
-rw-r----- 1 oracle dba 625 Nov 10 12:46 icai11_ora_2514.trc
-rw-r----- 1 oracle dba 626 Nov 10 12:48 icai11_ora_2626.trc
-rw-r----- 1 oracle dba 731 Nov 10 12:49 icai11_ora_2322.trc
-rw-r----- 1 oracle dba 1312 Nov 10 12:49 icai11_ora_2096.trc
-rw-r----- 1 oracle dba 625 Nov 10 12:50 icai11_ora_2315.trc
-rw-r----- 1 oracle dba 625 Nov 10 12:50 icai11_ora_1390.trc
-rw-r----- 1 oracle dba 729 Nov 10 12:51 icai11_ora_1990.trc
-rw-r----- 1 oracle dba 626 Nov 10 12:52 icai11_ora_2485.trc
-rw-r----- 1 oracle dba 626 Nov 10 12:52 icai11_ora_2063.trc
-rw-r----- 1 oracle dba 644 Nov 10 12:53 icai11_ora_2605.trc
-rw-r----- 1 oracle dba 626 Nov 10 12:54 icai11_ora_2299.trc
-rw-r----- 1 oracle dba 625 Nov 10 13:07 icai11_ora_2333.trc
-rw-r----- 1 oracle dba 626 Nov 10 13:07 icai11_ora_2380.trc
-rw-r----- 1 oracle dba 729 Nov 10 13:07 icai11_ora_2174.trc
-rw-r----- 1 oracle dba 625 Nov 10 13:08 icai11_ora_2851.trc
-rw-r----- 1 oracle dba 613 Nov 10 13:08 icai12_ora_627.trc
-rw-r----- 1 oracle dba 626 Nov 10 13:11 icai11_ora_2894.trc
-rw-r----- 1 oracle dba 1365 Nov 10 13:12 icai11_ora_2443.trc
-rw-r----- 1 oracle dba 1640016 Nov 10 13:42 icai12_ora_427.trc
-rw-r----- 1 oracle dba 676 Nov 10 13:48 icai11_ora_2183.trc
-rw-r----- 1 oracle dba 626 Nov 10 13:48 icai11_ora_2230.trc
-rw-r----- 1 oracle dba 645 Nov 10 13:55 icai11_ora_3220.trc
-rw-r----- 1 oracle dba 675 Nov 10 13:57 icai12_ora_276.trc
-rw-r----- 1 oracle dba 625 Nov 10 14:07 icai11_ora_3198.trc
-rw-r----- 1 oracle dba 1376 Nov 10 14:08 icai11_ora_2935.trc
-rw-r----- 1 oracle dba 625 Nov 10 14:09 icai11_ora_3273.trc
-rw-r----- 1 oracle dba 677 Nov 10 14:10 icai11_ora_2465.trc
-rw-r----- 1 oracle dba 634 Nov 10 14:17 icai12_ora_1137.trc
-rw-r----- 1 oracle dba 687 Nov 10 14:21 icai11_ora_1971.trc
-rw-r----- 1 oracle dba 688 Nov 10 14:23 icai11_ora_2973.trc
-rw-r----- 1 oracle dba 626 Nov 10 14:25 icai11_ora_2144.trc
-rw-r----- 1 oracle dba 770 Nov 10 14:32 icai12_ora_399.trc
-rw-r----- 1 oracle dba 718 Nov 10 14:37 icai12_ora_917.trc
-rw-r----- 1 oracle dba 644 Nov 10 14:48 icai11_ora_3510.trc
-rw-r----- 1 oracle dba 645 Nov 10 15:31 icai11_ora_2957.trc
-rw-r----- 1 oracle dba 730 Nov 10 15:33 icai11_ora_1973.trc
-rw-r----- 1 oracle dba 688 Nov 10 15:56 icai11_ora_3830.trc
-rw-r----- 1 oracle dba 2527 Nov 10 16:11 icai12_ora_364.trc
-rw-r----- 1 oracle dba 687 Nov 10 16:34 icai11_ora_4150.trc
-rw-r----- 1 oracle dba 1332 Nov 10 16:35 icai11_ora_3760.trc
-rw-r----- 1 oracle dba 715 Nov 10 16:38 icai11_ora_3723.trc
-rw-r----- 1 oracle dba 687 Nov 10 16:46 icai11_ora_4295.trc
-rw-r----- 1 oracle dba 714 Nov 10 16:56 icai11_ora_2598.trc
-rw-r----- 1 oracle dba 615 Nov 10 17:06 icai12_ora_2232.trc
-rw-r----- 1 oracle dba 615 Nov 10 17:09 icai12_ora_2290.trc
-rw-r----- 1 oracle dba 2527 Nov 10 17:13 icai12_ora_1875.trc
-rw-r----- 1 oracle dba 688 Nov 10 17:18 icai11_ora_4473.trc
-rw-r----- 1 oracle dba 978 Nov 10 17:25 icai12_ora_2265.trc
-rw-r----- 1 oracle dba 645 Nov 10 17:29 icai11_ora_4582.trc
-rw-r----- 1 oracle dba 730 Nov 10 17:36 icai11_ora_4084.trc
-rw-r----- 1 oracle dba 616 Nov 10 17:46 icai12_ora_2281.trc
-rw-r----- 1 oracle dba 615 Nov 10 17:46 icai12_ora_1811.trc
-rw-r----- 1 oracle dba 730 Nov 10 17:50 icai11_ora_4225.trc
-rw-r----- 1 oracle dba 2528 Nov 10 18:08 icai12_ora_2352.trc
-rw-r----- 1 oracle dba 626 Nov 10 18:10 icai11_ora_2501.trc
-rw-r----- 1 oracle dba 738 Nov 10 18:10 icai11_ora_2790.trc
-rw-r----- 1 oracle dba 688 Nov 10 18:28 icai11_ora_3768.trc
-rw-r----- 1 oracle dba 626 Nov 10 18:33 icai11_ora_4029.trc
-rw-r----- 1 oracle dba 626 Nov 10 18:33 icai11_ora_3965.trc
root@ai2 #You seem to have RAC with multiple instances.
Anyhow, lower(d.value) --> icai, doesn't occur in any filename. This is because the instance name is in the trace filename, not the database name.
You are aware you can set the tracefile_identifier?
This will be simply appended to the original filename.
Sybrand Bakker
Senior Oracle DBA -
[Deployment] How NOT to hard code the Database SID, Username, and Password
Hi, I'm new in J2EE so be easy on me. :)
How can I parameterize the database SID, username, and password in my J2EE application? So that anyone can change the SID, username, and password without the need to modify my code? I use Oracle 10g, ADF BC, JSF and JDeveloper 10.1.3.1.
My friend said that I can use XML for this. But he didn't go to detail for doing this. Is it true? Is there any [or better alternative]?
Any help or pointer to a simple tutorial would be fine.
Thanks in advance.Hi -- this is quite easy to do with J2EE.
In your application code, you declare "logical" references to resources (such as datasources, security roles, etc.) and use those in your application code so all it depends on is the logical name
On the server where the application is deployed, "physical" resources are created that point to the actual resource -- in the case of a database, this would be the JDBC URL, username, password.
At deployment time of the application, you then use the facilities of deployment tool to "map" the logical references in the application, to the physical references that exist on the server. So you connect the dots between your application needing something and the server providing the something. That way all the "details" are abstracted out of the your application code.
I don't know how this works in ADF, BC4J, etc. but I presume that since they are based on standard/J2EE, it must be available somehow.
I wrote something about this a while back using direct JDBC as an example:
http://buttso.blogspot.com/2006/06/datasource-lookup-using-javacompenv.html
-steve- -
"Application is bound to side-by-side" problem
Hello,
I have been working on an application for several months now. I started developing for Air 1.5 and when the 2.0 beta came out I downloaded the SDK and updated my application's namespace and it worked fine.
Now that the official 2.0 version is released and the "2.0beta2" namespace is not supported anymore my application wouldn't install, or even run when I installed the new AIR runtime.
I downloaded the updated SDK, replaced the old one (I'm using Flash CS4 to package and build the application), changed the namespace to "2.0" and re-exported my application.
It installed with no problems and I can run it perfectly on the computer I am developing from. However if I try to install the exact same .air file on any other machine (Windows or Mac) i get the classic: "The application could not be installed because the installer file is damaged."
My .airappinstall.log reads:
UI SWF load is complete
UI initialized
Unpacking to C:\Users\ec\AppData\Local\Temp\fla3CFD.tmp
unpacking is complete
application is bound to side-by-side version null
Downloading a runtime update from http://airdownload.adobe.com/air/3/windows/x86/add/2.0beta2/update to C:\Users\ec\AppData\Roaming\Adobe\AIR\Updater\1.0
No update available
starting cleanup of temporary files
application installer exiting
Does anyone have any insight to this? Like I said, I am sure my application descriptor file has this namespace: <application xmlns="http://ns.adobe.com/air/application/2.0">
I am packaging and exporting the application from Flash CS4, and I did changed the SDK when the beta came out, but I overlay it with the new one already (before if wouldn't even let me export).
Thank you in advance.This is just an update, when I install the .air on the computer I'm developing, it installs with no problems like I said, and this is what it traces on the airappinstall.log:
Starting silent app install of file:///Volumes/Adobe%20Flash%20Professional%20CS5/Adobe%20Flash%20Professional%20CS5/pay loads/AdobeAMP1.8-mul/adobe_media_player.air
UI SWF load is complete
UI initialized
Unpackaging to /private/var/folders/zz/zzzivhrRnAmviuee+++++++++++/TemporaryItems/FlashTmp0
unpackaging is complete
application is bound to side-by-side version 1.0
application is bound to this version of the runtime
app id com.adobe.amp
pub id 4875E02D9FB21EE389F73B8D1702B320485DF8CE.1
Application located at /Applications
bad configuration for silent install or update
starting cleanup of temporary files
application installer exiting
why is "application is bound to this version of the runtime". Is there something I haven't done on the Flash CS4 folder?
Thank you. -
The application Activity Monitor quit unexpectedly
Activity Monitor refuses to startup since installing Leopard on this MacBook. Everything else seems to be working properly.
A search didn't turn up anyone else having this problem... anyone have a clue?
ThanksI also have the same problem. I follow the instructions above, however the problem persists.
Here is my system log:
[0x0-0x3d03d].com.apple.ActivityMonitor[358]: dyld: lazy symbol binding failed: Symbol not found: __commpagedsmos
[0x0-0x3d03d].com.apple.ActivityMonitor[358]: Referenced from: /Applications/Activity Monitor.app/Contents/MacOS/Activity Monitor
[0x0-0x3d03d].com.apple.ActivityMonitor[358]: Expected in: /usr/lib/libSystem.B.dylib
[0x0-0x3d03d].com.apple.ActivityMonitor[358]: dyld: Symbol not found: __commpagedsmos
ReportCrash[360]: Formulating crash report for process Activity Monitor[358]
([0x0-0x3d03d].com.apple.ActivityMonitor[358]): Exited abnormally: Trace/BPT trap
Here is the detailed crash log:
Process: Activity Monitor [358]
Path: /Applications/Activity Monitor.app/Contents/MacOS/Activity Monitor
Identifier: com.apple.ActivityMonitor
Version: 1.5.3 (58)
Build Info: ActivityMonitor-580000~1
Code Type: X86 (Native)
Parent Process: launchd [132]
Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0
Dyld Error Message:
Symbol not found: __commpagedsmos
Referenced from: /Applications/Activity Monitor.app/Contents/MacOS/Activity Monitor
Expected in: /usr/lib/libSystem.B.dylib -
SQL1119N A connection to or activation of database "DEV"
Hello All,
am Gautam Poddar from PwC, Kolkata. I have talked with you just now.
We have activated the logretain and userexit on after taking the full ofline backup of the system. We were unable to take the online backup, so log directory was full. So we have moved the log file from log directory to another directory. After that we have increased the size of the log directory and copy all the log files to log directory but database connection is failed. I am getting this error while try to connect with this command > connect to dev
SQL1042C An unexpected system error occurred. SQLSTATE=58004
Yesterday I was unable to resolve the problem. So I have restored all the file system from OS level Backup. Now I am not able to connect the Database and it is giving this error message
ecldevqa:db2dev 5> db2 connect to DEV
SQL1119N A connection to or activation of database "DEV" cannot be made
because a previous restore is incomplete. SQLSTATE=57019
Restored these file system
/dev/sapvg/devsaptemp1
1572864 16768 1544008 1% /db2/DEV/saptemp1
/dev/sapvg/devsapdata4
41943040 23979664 17823088 57% /db2/DEV/sapdata4
/dev/sapvg/devsapdata3
41943040 23979664 17823088 57% /db2/DEV/sapdata3
/dev/sapvg/devsapdata2
41943040 23979664 17823088 57% /db2/DEV/sapdata2
/dev/sapvg/devsapdata1
41943040 23979664 17823088 57% /db2/DEV/sapdata1
/dev/sapvg/DEV_LOG_DIR
10485760 5390328 5055680 52% /db2/DEV/log_dir
/dev/sapvg/devdb2dump
3145728 2757168 385592 88% /db2/DEV/db2dump
/dev/sapvg/db2dev 3145728 100224 3021728 3% /db2/db2dev
I have seen these out put has not changed after restoration > db2 get db cfg for DEV
ecldevqa:db2dev 17> db2 get db cfg for DEV
Database Configuration for Database DEV
Database configuration release level = 0x0b00
Database release level = 0x0b00
Database territory = en_US
Database code page = 1208
Database code set = UTF-8
Database country/region code = 1
Database collating sequence = IDENTITY_16BIT
Alternate collating sequence (ALT_COLLATE) =
Database page size = 16384
Dynamic SQL Query management (DYN_QUERY_MGMT) = DISABLE
Discovery support for this database (DISCOVER_DB) = ENABLE
Restrict access = NO
Default query optimization class (DFT_QUERYOPT) = 5
Degree of parallelism (DFT_DEGREE) = 1
Continue upon arithmetic exceptions (DFT_SQLMATHWARN) = NO
Default refresh age (DFT_REFRESH_AGE) = 0
Default maintained table types for opt (DFT_MTTB_TYPES) = SYSTEM
Number of frequent values retained (NUM_FREQVALUES) = 10
Number of quantiles retained (NUM_QUANTILES) = 20
Backup pending = NO
Database is consistent = NO
Rollforward pending = NO
Restore pending = NO
Multi-page file allocation enabled = YES
Log retain for recovery status = NO
User exit for logging status = YES
Self tuning memory (SELF_TUNING_MEM) = OFF
Size of database shared memory (4KB) (DATABASE_MEMORY) = COMPUTED
Database memory threshold (DB_MEM_THRESH) = 10
Max storage for lock list (4KB) (LOCKLIST) = 20000
Percent. of lock lists per application (MAXLOCKS) = 90
Package cache size (4KB) (PCKCACHESZ) = 5120
Sort heap thres for shared sorts (4KB) (SHEAPTHRES_SHR) = 20000
Sort list heap (4KB) (SORTHEAP) = 2048
Database heap (4KB) (DBHEAP) = 35000
Catalog cache size (4KB) (CATALOGCACHE_SZ) = 2560
Log buffer size (4KB) (LOGBUFSZ) = 1024
Utilities heap size (4KB) (UTIL_HEAP_SZ) = 10000
Buffer pool size (pages) (BUFFPAGE) = 10000
Max size of appl. group mem set (4KB) (APPGROUP_MEM_SZ) = 128000
Percent of mem for appl. group heap (GROUPHEAP_RATIO) = 25
Max appl. control heap size (4KB) (APP_CTL_HEAP_SZ) = 1600
SQL statement heap (4KB) (STMTHEAP) = 5120
Default application heap (4KB) (APPLHEAPSZ) = 4096
Statistics heap size (4KB) (STAT_HEAP_SZ) = 15000
Interval for checking deadlock (ms) (DLCHKTIME) = 10000
Lock timeout (sec) (LOCKTIMEOUT) = 3600
Changed pages threshold (CHNGPGS_THRESH) = 40
Number of asynchronous page cleaners (NUM_IOCLEANERS) = AUTOMATIC
Number of I/O servers (NUM_IOSERVERS) = AUTOMATIC
Index sort flag (INDEXSORT) = YES
Sequential detect flag (SEQDETECT) = YES
Default prefetch size (pages) (DFT_PREFETCH_SZ) = AUTOMATIC
Track modified pages (TRACKMOD) = ON
Default number of containers = 1
Default tablespace extentsize (pages) (DFT_EXTENT_SZ) = 2
Max number of active applications (MAXAPPLS) = AUTOMATIC
Average number of active applications (AVG_APPLS) = AUTOMATIC
Max DB files open per application (MAXFILOP) = 1950
Log file size (4KB) (LOGFILSIZ) = 16380
Number of primary log files (LOGPRIMARY) = 20
Number of secondary log files (LOGSECOND) = 40
Changed path to log files (NEWLOGPATH) =
Path to log files = /db2/DEV/log_dir/NODE
0000/
Overflow log path (OVERFLOWLOGPATH) =
Mirror log path (MIRRORLOGPATH) =
First active log file = S0000062.LOG
Block log on disk full (BLK_LOG_DSK_FUL) = YES
Percent max primary log space by transaction (MAX_LOG) = 0
Num. of active log files for 1 active UOW(NUM_LOG_SPAN) = 0
Group commit count (MINCOMMIT) = 1
Percent log file reclaimed before soft chckpt (SOFTMAX) = 300
Log retain for recovery enabled (LOGRETAIN) = OFF
User exit for logging enabled (USEREXIT) = OFF
HADR database role = STANDARD
HADR local host name (HADR_LOCAL_HOST) =
HADR local service name (HADR_LOCAL_SVC) =
HADR remote host name (HADR_REMOTE_HOST) =
HADR remote service name (HADR_REMOTE_SVC) =
HADR instance name of remote server (HADR_REMOTE_INST) =
HADR timeout value (HADR_TIMEOUT) = 120
HADR log write synchronization mode (HADR_SYNCMODE) = NEARSYNC
First log archive method (LOGARCHMETH1) = OFF
Options for logarchmeth1 (LOGARCHOPT1) =
Second log archive method (LOGARCHMETH2) = OFF
Options for logarchmeth2 (LOGARCHOPT2) =
Failover log archive path (FAILARCHPATH) =
Number of log archive retries on error (NUMARCHRETRY) = 5
Log archive retry Delay (secs) (ARCHRETRYDELAY) = 20
Vendor options (VENDOROPT) =
Auto restart enabled (AUTORESTART) = ON
Index re-creation time and redo index build (INDEXREC) = SYSTEM (RESTART)
Log pages during index build (LOGINDEXBUILD) = OFF
Default number of loadrec sessions (DFT_LOADREC_SES) = 1
Number of database backups to retain (NUM_DB_BACKUPS) = 12
Recovery history retention (days) (REC_HIS_RETENTN) = 60
TSM management class (TSM_MGMTCLASS) =
TSM node name (TSM_NODENAME) =
TSM owner (TSM_OWNER) =
TSM password (TSM_PASSWORD) =
Automatic maintenance (AUTO_MAINT) = ON
Automatic database backup (AUTO_DB_BACKUP) = OFF
Automatic table maintenance (AUTO_TBL_MAINT) = ON
Automatic runstats (AUTO_RUNSTATS) = ON
Automatic statistics profiling (AUTO_STATS_PROF) = OFF
Automatic profile updates (AUTO_PROF_UPD) = OFF
Automatic reorganization (AUTO_REORG) = OFF
Before restoration it was "First active log file = S0000062.LOG" and after restoration this parameter has not changed.
db2diag.log >
INSTANCE: db2dev NODE : 000
FUNCTION: DB2 UDB, routine_infrastructure, sqlerFmpListener, probe:999
MESSAGE : FMP exiting with error. Last agent registered:
DATA #1 : Hexdump, 4 bytes
0x9FFFFFFFFFFFEEE4 : 0000 0000 ....
2008-01-30-10.34.12.283359+330 I2618633502A1630 LEVEL: Event
PID : 12514 TID : 1 PROC : db2start
INSTANCE: db2dev NODE : 000
FUNCTION: DB2 UDB, base sys utilities, sqleStartStopSingleNode, probe:1130
DATA #1 : String, 31 bytes
/db2/db2dev/sqllib/adm/db2star2
DATA #2 : Hexdump, 256 bytes
0x9FFFFFFFFFFFBBC0 : 2F64 6232 2F64 6232 6465 762F 7371 6C6C /db2/db2dev/sqll
0x9FFFFFFFFFFFBBD0 : 6962 2F61 646D 2F64 6232 7374 6172 3200 ib/adm/db2star2.
0x9FFFFFFFFFFFBBE0 : 4E4F 4D53 4700 0000 0000 0000 0000 0000 NOMSG...........
0x9FFFFFFFFFFFBBF0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x9FFFFFFFFFFFBC00 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x9FFFFFFFFFFFBC10 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x9FFFFFFFFFFFBC20 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x9FFFFFFFFFFFBC30 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x9FFFFFFFFFFFBC40 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x9FFFFFFFFFFFBC50 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x9FFFFFFFFFFFBC60 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x9FFFFFFFFFFFBC70 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x9FFFFFFFFFFFBC80 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x9FFFFFFFFFFFBC90 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x9FFFFFFFFFFFBCA0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
0x9FFFFFFFFFFFBCB0 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
2008-01-30-10.34.14.121256+330 E2618635133A1198 LEVEL: Event
PID : 12517 TID : 1 PROC : db2star2
INSTANCE: db2dev NODE : 000
FUNCTION: DB2 UDB, base sys utilities, DB2StartMain, probe:911
MESSAGE : ADM7513W Database manager has started.
START : DB2 DBM
DATA #1 : Build Level, 152 bytes
Instance "db2dev" uses "64" bits and DB2 code release "SQL09011"
with level identifier "01020107".
Informational tokens are "DB2 v9.1.0.1", "s061104", "U809678", Fix Pack "1".
DATA #2 : System Info, 104 bytes
System: HP-UX ecldevqa B.11.23 U ia64
CPU: total:6 online:6 Threading degree per core:1
Physical Memory(MB): total:16354 free:9294
Virtual Memory(MB): total:49122 free:42062
Swap Memory(MB): total:32768 free:32768
Kernel Params: msgMaxMessageSize:65535 msgMsgMap:2048 msgMaxQueueIDs:512
msgNumberOfHeaders:2046 msgMaxQueueSize:65535
msgMaxSegmentSize:96 shmMax:17179869184 shmMin:1 shmIDs:400
shmSegments:300 semMap:2050 semIDs:2048 semNum:4096
semUndo:1024 semNumPerID:2048 semOps:500 semUndoPerProcess:100
semUndoSize:824 semMaxVal:32767 semAdjustOnExit:16384
2008-01-30-10.34.50.661312+330 I2618636332A365 LEVEL: Warning
PID : 12533 TID : 1 PROC : db2agent (DEV) 0
INSTANCE: db2dev NODE : 000
APPHDL : 0-7 APPID: *LOCAL.db2dev.080130050450
AUTHID : DB2DEV
FUNCTION: DB2 UDB, base sys utilities, sqleCheckForRestore, probe:10
RETCODE : ZRC=0xFFFFFBA1=-1119
2008-01-30-10.34.50.662169+330 I2618636698A373 LEVEL: Warning
PID : 12533 TID : 1 PROC : db2agent (DEV) 0
INSTANCE: db2dev NODE : 000
APPHDL : 0-7 APPID: *LOCAL.db2dev.080130050450
AUTHID : DB2DEV
FUNCTION: DB2 UDB, base sys utilities, sqlePrepareForSerialization, probe:20
RETCODE : ZRC=0xFFFFFBA1=-1119
2008-01-30-10.34.50.662288+330 I2618637072A353 LEVEL: Severe
PID : 12533 TID : 1 PROC : db2agent (DEV) 0
INSTANCE: db2dev NODE : 000
APPHDL : 0-7 APPID: *LOCAL.db2dev.080130050450
AUTHID : DB2DEV
FUNCTION: DB2 UDB, base sys utilities, sqleserl, probe:10
RETCODE : ZRC=0xFFFFFBA1=-1119
2008-01-30-10.43.19.986356+330 I2618637426A365 LEVEL: Warning
PID : 12532 TID : 1 PROC : db2agent (DEV) 0
INSTANCE: db2dev NODE : 000
APPHDL : 0-10 APPID: *LOCAL.db2dev.080130051319
AUTHID : DB2DEV
FUNCTION: DB2 UDB, base sys utilities, sqleCheckForRestore, probe:10
RETCODE : ZRC=0xFFFFFBA1=-1119
2008-01-30-10.43.19.987187+330 I2618637792A373 LEVEL: Warning
PID : 12532 TID : 1 PROC : db2agent (DEV) 0
INSTANCE: db2dev NODE : 000
APPHDL : 0-10 APPID: *LOCAL.db2dev.080130051319
AUTHID : DB2DEV
FUNCTION: DB2 UDB, base sys utilities, sqlePrepareForSerialization, probe:20
RETCODE : ZRC=0xFFFFFBA1=-1119
2008-01-30-10.43.19.987305+330 I2618638166A353 LEVEL: Severe
PID : 12532 TID : 1 PROC : db2agent (DEV) 0
INSTANCE: db2dev NODE : 000
APPHDL : 0-10 APPID: *LOCAL.db2dev.080130051319
AUTHID : DB2DEV
FUNCTION: DB2 UDB, base sys utilities, sqleserl, probe:10
RETCODE : ZRC=0xFFFFFBA1=-1119
ecldevqa:db2dev 20>
Thanks & Regards,
Gautam Poddar
SAP BASIS
PricewaterhouseCoopers (P) LimitedHi Gautam
As Adam said ....
1. never manually move db2 active log files
2. IBM does not support filesystem restores.
The only solution for you is to restore the offline backup and if you have archive logs, then you can do a rollforward .
Amit
Edited by: amit chak on Aug 19, 2008 8:07 PM -
No sap data found in the database SID !
Hello All,
While doing BI system copy activity, we are getting message as no sap data found in the database <SID>! and we could not able to proceed further.
We have MS SQL 2005 as DB and Windows 2003 STD as our OS. We are doing the system copy through homogeneous system copy method (Backup / Restore).
Before running SAPint we had deleted the old database then restored the database from the backup which we had taken of our production system.
We also ran the SQL script user_change.sql as per the note # 551915 but in SAPint we are getting above mentioned error.
Could you please help me in this regard ?
Best Regards,
Amit VaijHi at all, I have the same error. But I'm wondering about the assumption, that the schema renaming should be the root cause.
I'm trying to copy a BI dual tack system on Windows/MSSQL database specific (http://scn.sap.com/thread/3380228)
Now I'm defining the parameters in SAPINST (SoftwareProvMngr), so at the moment in no step I've to set up any old schema. Also I'm not at the step of defining the JAVA export.
At the moment the SAPINST tool is trying to connect the main SAP DB.
I attached and renamed the ABAP part of the DB. I will now try to detach the DB, I assume the SAPINST Tool will install to an empty DB. So if you attach a DB with a wrong schema it can not find any tables in the instance shema of the SID defined in SAPINST and it work... we will see...
Detach was the wrong Idea... it seems there is any issue with the permissions...
but R3trans -d works -
Add database SID to window title
Is there a way to append the database SID to the webformsTitle in the formsweb.cfg? I would like to use the same formsweb.cfg file for both test and prod, but be able to see which database I am connected to on the title bar.
Hi,
you could add the database name to the Browser title. Just add
pageTitle= ORCL_Prod
to the application definition of your application in formsweb.cfg. You can set this value in the default section, if it should be the same for all applications.
Alternatively, you can pass the database name as a parameter to Forms and set it there as a window property.
Frank -
Hi,
My company is a partner of SAP and we supply Crystal Reports Server along with our web application for reports generation
My questions are
1. When a user generates a report from the web application what actions/processes/other actions are taking place on the client side and which actions are taken on the database side
2. what is the workflow since the user generates a report until the result set is displayed in the web browser?
I also like to know where each report component (e.g. sub report, formula, parameter, etc.) is being processed
Thanks
BarryHope below link may help you out to understad the Architecture
http://www.sdn.sap.com/irj/scn/elearn?rid=/library/uuid/90e4769d-3ebb-2c10-ac82-e90de7c73185&overridelayout=true
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/50af0f39-4cd0-2c10-da84-eb8c957500b1?quicklink=index&overridelayout=true
http://media.wiley.com/product_data/excerpt/00/07645573/0764557300.pdf -
Uploading the data from Application server to Database
Hi,
I am trying to upload tab delimited file from application server into database.
I have upload the file from presentation to application server by CGZ3
and i am able to see file in app server with #s and it appers in application server as
10140#A#E#120#abcd#
10146#M#P#300#a.b#
10152#M#P#200#dat123.com##
140#A#P#300#blicksat123.com#
10140#A#E#260#cust1at123.com##
And my notepad records looks like
10140 A E 120 abcd
10146 M P 300 a.b
10152 M P 200 dat123.com
140 A P 300 blicksat123.com
10140 A E 260 cust1at123.com
I am using open data set and read dataset to read the file as shown below
DATA:
l_htab TYPE c, " Horizontal tab
l_line(100) TYPE c. " Content in the file
l_htab = cl_abap_char_utilities=>horizontal_tab.
Open dataset
OPEN DATASET pp_afname FOR INPUT IN TEXT MODE ENCODING DEFAULT.
IF sy-subrc EQ 0.
DO.
Read dataset
READ DATASET pp_afname INTO l_line.
IF sy-subrc EQ 0.
SPLIT l_line AT l_htab
INTO fs_file-carrid
fs_file-autoind
fs_file-commtype
fs_file-resptime
fs_file-smtpaddr.
APPEND fs_file TO pt_afile.
ELSE.
EXIT.
ENDIF. " IF SY-SUBRC EQ 0.
ENDDO. " DO.
CLOSE DATASET pp_afname.
ELSE.
MESSAGE 'Problem in opening the App.Server file' TYPE con_msgtyp_i.
ENDIF. " IF sy-subrc EQ 0.
Load the data to the database
PERFORM load_data_to_database USING t_afile.
When i am trying to upload it is taking me to dump and the errpr analysis is like
"The program attempted to interpret the value "26 0 " as a number, but
since the value contravenes the rules for correct number formats,
this was not possible."
Any suggestions on this
Regards
VEnk@Hi,
Thats the line feed character. After reading the application server file, use this
data: lv_feed type c value CL_ABAP_CHAR_UTILITIES=>CR_LF.
loop at itab.
replace all occurrences of lv_feed in itab-field with space.
modify itab.
endloop.
Vikranth -
What is the link between PO and Requisition in database side
hello friends,
please can any one tell me that what is the link between PO and Requisition in database side. means after creating the requisition we will go for create the PO based on that requisition.
want to know that what is the link between both in database side.
Thanks in advance
krish.Hi,
The link is at distribution level, between:
PO_DISTRIBUTIONS_ALL.REQ_DISTRIBUTION_ID
and
PO_REQ_DISTRIBUTIONS_ALL.DISTRIBUTION_ID
Hope it helps. -
Multiple OID schema's in a single database SID?
I have OID/OVD 11g installed in a development environment and during the install I used the create schema option to automatically create the required database schema. I now need to install a second seperate instance of OID/OVD, but the database schema will reside in the same database SID.
Is this possible as presumably the script will be trying to create users/tablespaces that already exist for the first instance?
I see you can install OID using an existing schema, but I'm assuming this needs to be empty and that there's on way two ldaps can share the same schema.
I guess I'm hoping the script is clever enough to modify it's user/tablespace naming details if they already exist, but this doesn't seem likely.
Any advice gratefully received.The existing schema doesnt have to be empty. If you select High Availability, the installer will automatically recognize that you want another instance of OID with the same database.
Maybe you are looking for
-
HP Pavilion 17-e066nr Notebook Laptop Motherboard Replacement
I just replaced the motherboard on the HP Pavilion 17-e066nr notebook laptop, and during startup I get an error saying the the serial number, model number, and product number is not recognized. Is there any way to input this information? I tried to
-
Hey all, I just upgraded my ram from 2gigs to 4gigs. Oh the difference is amazing, I am quite supprised. And ram is cheap right now. I got 2gigs for $100.00 at OWC. COME TO THE LIGHT!
-
Maybe I'm missing something obvious, but I can't figure out how to create hyperlinks within a page in iWeb. Specifically, I'm trying to write a FAQ, and want to link individual questions listed at the top of the page with their answers further down i
-
Purchased a new desktop and when I try and download prior music purchases, I'm told I need to authorize my computer for the download.. Any ideas? Thank you.
-
Why am I seeing text typed over the TOP of text, when I'm filling in the spaces of an application? I have Adobe XI. I chose the hand tool, and highlighted the form. It IS a fillable form. Any ideas? Also, I don't see a "submit" button so I can em