SRM system copy
Hello All,
One of our IT partners has got an SAP SRM implementation and we need to set up our own SRM system as a copy of the partner's SRM system.
How can we do this? What system copy approach we can follow?Will DB restore work?
During the copy will it ask for any hardware/software keys?
Do we need to seperately buy the licenses ?
Our OS/DB is going to be different from that of the partner.
Please give me a high level idea.
Regards
Arun
Arun,
Check below sap notes, links & details.
SAP Note 547314 FAQ: System Copy procedure
SAP Note 89188 - R/3 System copy
System Copy and Migration
https://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/b055e88d-f040-2a10-e390-862b4aedb339
System Refresh
How can we do this? What system copy approach we can follow?Will DB restore work?
You can do this by homogeneous system copy. Yes DB restore method will work.
During the copy will it ask for any hardware/software keys?
No it will not ask for any keys(Homogeneous system copy not sure about heterogeneous system copy)
Do we need to separately buy the licenses ?
No
Our OS/DB is going to be different from that of the partner
The copy of an SAP system to another hardware is called a system copy. If the target system will run on a different operating system (OS) and/or a different database system (DB) than the source system, then this is called a heterogeneous system copy or OS/DB migration. Check below link for detail
https://websmp108.sap-ag.de/osdbmigration
Note 82478 - SAP system OS/DB migration
You can download system copy guide from below link
https://websmp203.sap-ag.de/instguides.
Homogeneous System Copy:-During the system copy you use the same operating system and database platform as the original
system.
Heterogeneous System Copy:-During the system copy, you change either the operating system or the database system, or both.
Heterogeneous system copy is a synonym for migration.
System Copy :-Duplication of an SAP system. Certain SAP parameters might change in a copy. When you
perform a system copy, SAPinst installs all the instances again, but it uses a copy of the source
system database to set up the database.
Database Copy :-Database-dependent part of the system copy.
Hope this helps
Thanks
Sushil
Edited by: Sushil Suryawanshi on Jun 2, 2009 2:12 AM
Edited by: Sushil Suryawanshi on Jun 2, 2009 2:21 AM
Similar Messages
-
Cannot change PO's in SRM due to system copy/ logical system error
Hi All-
We are running SRM extended classic scenario. We would like to change PO's that have been created in our production system, but copied to another environment. We are trying to change these PO's in the copied system but are getting error messages in the process purchase orders transaction in SRM, and are not allowed to change the PO's. The message reads "purchase order contains items with different logical systems". Our basis team changes the logical systems as part of our system copies. Has anyone experienced this? I this part of standard SAP functionality? Are their logical systems in any of the transactional data(PO) tables that we need to change?
Also, we are deleting the material group/product hierarchy in comm_hierarchy as part of our system copy tasks because the material groups each have a GUI ID that is system dependent. Could this have something to do with our issue? Any feedback is greatly appreciated.
Thanks.Hey John,
Yes I'm still at CA. How are you?
I checked bbp_pd and the logical systems are changed correctly to the copied system, not set to production. Am I missing something here? Should they be set to production logical system names even though I am trying to change the PO in the copied system?
Thanks! -
System Copy using SAPINST on SRM 5.0 + DB MSSQL 2003 + OS Win 2003 Server
Hi All,
Im doing a System Copy using export and import method i.e using SAPINST. Export has been completed and now when im doing the import. it stops at Import Java dump and give me this error in
Jload.java.log
Apr 23, 2009 5:29:56 PM com.sap.inst.jload.Jload logStackTrace
SEVERE: com.sap.dictionary.database.dbs.JddException: CREATE TABLE CAF_RT_MAPRLE failed
17:29:56 2009-04-23 dbs-Info: <<< Analyze table CAF_RT_MAPRLE >>>
17:29:56 2009-04-23 dbs-Info: predefined action is: >>>null<<<
17:29:56 2009-04-23 mss-Info: table CAF_RT_MAPRLE doesn't contain data
17:29:56 2009-04-23 dbs-Info: Action: DROP_CREATE
17:29:56 2009-04-23 ope-Info: Action: DROP_CREATE not possible
at com.sap.inst.jload.db.DBTable.create(DBTable.java:109)
at com.sap.inst.jload.Jload.dbImport(Jload.java:278)
at com.sap.inst.jload.Jload.executeJob(Jload.java:397)
at com.sap.inst.jload.Jload.main(Jload.java:621)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.sap.engine.offline.OfflineToolStart.main(OfflineToolStart.java:81)
Apr 23, 2009 5:29:56 PM com.sap.inst.jload.db.DBConnection disconnect
INFO: disconnected
Has any one seen this error ???
Regards,
Ershad AhmedHi,
I would refer the concerned System copy guide "[System Copy for SAP Systems Based on NW 7.0 SR2 ABAP+Java|https://websmp108.sap-ag.de/~sapdownload/011000358700006457662006E/SYSCOPY_2004sSR2_ABAPJava.pdf] " along with this [SAP Note 151603 - Copying an SQL Server database|https://service.sap.com/sap/support/notes/151603] for getting all answers.
All prerequisites / steps are well mentioned in that documents. Please read them carefully.
Regards,
Bhavik G. Shroff -
Logical system name in SRM system
We are into SRM version 5.(SRM server 5.5) with the backend system as SAP ECC 6.0 .
The logical system is defined as '0000000050' for backend SAP system . All the systems like CRM and BW uses this as the logical system name for backend system . Recently SRM is implemented in our organization and we have no other choice and have to use the logical system name as '0000000050'
When product categories are assigned in the org attributes , the system stores the back end system as 50 and this is the issue. SAP support mentions that this is issue with logical system naming convention and that need to be fixed . But they fail to understand that the same name works fine in all other systems and also in SRM system except product categories .
Is there any OSS note for this fix. I would like to hear your experiences in this scenario.
Thanks
ManiHi Mani,
Logical System names are system specific, hence you have a different name in SRM system which will represent your backend system and this is not at all an issue. As suggested by SAP; '0000000050' is not the best name as per best practices.
You should have a name which should be of the pattern: <SID>CLNT<Client Number>.
Now here is the solution/work around. But be very careful and try this in sandbox system before being carried out in Dev/QA/PRD systems. Please make sure no other users are performing any activity while these tasks are being carried out.
In addition, please read through the ["Set up and system copy of SRM server 5.5";|https://websmp204.sap-ag.de/~sapidb/011000358700000310782007E/SRM50_SetupTranspCopy.pdf] guide before you carry out this activity:
The below activities are to be carried out only in SRM system
I assume SRM & Backend are separate instances
1. Create a new logical system name for the backend system in SRM system as per the standard suggested above.
2. Then use the transaction BDLS, to convert the old logical system name to new logical system name in all the tables.
3. Now, the step 2 ensure the logical system name is converted appropriately in all tables except SRM Org Structure related table.
4. Use the report RHOMATTRIBUTES_REPLACE, for replacing all the old logical system value with new logical system value. Please note while providing the inputs in the screen, there will be a Checkbox field called "Sub-String", you must check this one for all attributes you enter in the report. Then when you execute the report, a list will be display, here you have to select all the rows and click the first button on the toolbar. Only then the attributes will be updated.
Please let me know, if further inputs are required.
Regards, Kathirvel -
Help in ABAP+JAVA Homogeneous System copy
Dear BASIS Gurus,
We have SRM 4.0, Portal 6.0, BW 3.5 and XI 3.0 based on WAS 640, all with
ABAP+JAVA stacks in HP-UX B.11/Oracle 9.2.x.
We are planning Homogeneous System copies to refresh our Development
environment.
After reading the instguides, I'm a litle confused about the best
strategy to use.
Using SAPINST in the source System to export the Database, I have the
dump files with Database data.
Do I must run SAPINST again to get the JAVA data (both database and
filesystem data)?
In the target system do I must do two runs of SAPINST ? One for ABAP
and other for JAVA?
Yhanks in adavnce.
Best regards.
Arnaldo Calçada.Hi Arnaldo,
There are basically two method of performing system copy.
1. Using database tool (you can use backup/restore procedure)
2. Using SAPINST tool (export/import)
This is applicable for both ABAP and JAVA.
Do I must run SAPINST again to get the JAVA data (both database and
filesystem data)?
It depends which method you are using.
In the target system do I must do two runs of SAPINST ? One for ABAP
and other for JAVA?
Yes if you are using 2nd method.
Hope this will help.
-Pinkle -
Is a system copy to development a best practice?
("Refresh", as I use it here, refers to a system copy.)
We typically refresh our sandbox and pre-production test systems from production. Not often, since its a non-trivial amount of work (although our functional/business teams don't seem to realize that ), but we've got the process down. The production DBs also total around 8-9 TB, and its not practical to store too many copies of that. The full environment includes the core ERP 6 system (HR, PY, FI, CO, parts of PLM), SRM 5, BI 7, and two portals (employee and vendor), each with development, QA/test, pre-production, and production.
We have never refreshed our development environment, mainly since that version history and test data.
We recently had a project consultant request that we refresh development from production, and claim doing so was a "best practice". The project might significantly reconfigure FI, but everything else is out of scope.
Although refreshing the development system/environment can be done, should it be? What kind of circumstances might make it a good idea? Is it considered it a "best practice" by others? Why?
(Cross posted to the [ASUG Systems Management forum|http://hosted.jivesoftware.asug.com/community/sig_communities/business_integration__technology_%26_infrastructure/systems_management_sig].)
Thanks,
DaveWell i cannot view the ASUG discussion but here is my 2 cents:
cons:
- versions history has to be saved prior to copy
- cost (additional disk space, backups, cpu/memory)
- the production data will age pretty fast, so the copy has to be done on a regular basis
- lots of interfaces to other systems will have to be corrected, risk of connecting to prod systems during the copy process
- the dev system will be unavailable for several days during the copy
pros:
- real data on the prod system, no need to manually generate data
- most performance issues can be discovered at design time, given the hardware is comparable to the prod system
In my opinion regularly copying the prod system to dev is not best practice. Personally i would never do it because of the cost and amount of work needed to do it.
Best regards, Michael -
Two SRM system in the same Portal
Dear Guru,
we need your support for the following question.
I'm working with SRM 7 and ECC in a extended classic scenario. SRM is available thorugh the portal. For training activity we need to have another copy of SRM and ECC system. It is possible to connect in the same time two SRM system in the unique portal?
Thanks a lot.
Best Regards
GiuseppeHello Giuseppe,
As per the standard , there is no possibility to work on twins SRM system at the same time on Portal. And as Ivy Li mentioned that all SRM IViews have system alias as SAP_SRM which points to 1 system at a time . Now as per your saying twins SRM system with unique portal which will also create a problem as most of the time the portal navigation would be locked.Now again while uploading the WDA package for SRM portal your data's might get effect if you are showing your actual data in your training session. If you find then there could be many reasons.
Regards
Gaurav Gautam -
SRM - System Refresh (Post Refresh steps)
Hi,
Can anyone tell me the steps to execute after SRM system refresh using file copy method ?
Thanks & Regards,
JagI have seen this somewhere in the forum: See if this helps you
BDLS: Convertion of logical system (SRM).
Check entry in table TWPURLSVR.
Check RFC connections (R/3 and SRM)
SPRO, check or set the following points:
Set up Distribution Model and distribute it
Define backend system
Define backend sytem per product category
Setting for vendor synchronization
Numbe ranges
Define object in backend sytem
Define external services (catalogs)
Check WF customizing: SWU3, settings for tasks
SICF: maintain the service BBPSTART, SAPCONNECT
SE38:
Run SIAC_PUBLISH_ALL_INTERNAL
Run BBP_LOCATIONS_GET_ALL
Update vendor BBPUPDVD
Check Middleware if used.
Run BBP_GET_EXRATE.
Schedule jobs (bbp_get_status2, clean_reqreq_up)
Convert attributes with RHOM_ATTRIBUTE_REPLACE
BR
Muthu -
SWPM - System Copy - Assertion Failed Unable to load database
Hello again,
(already the next question form me, sorry for this
I am executing a sysetm copy (DB-refresh) on ASE using SWPM.
However, in "Configure Components" step I get the error: Assertion failed. Unable to load database <SID of Target Sysetm>.
Where else can I check for errors?
I think it is still something on which I already worked (with other thread).
In sapinst_dev.log I found this
TRACE 2015-03-25 11:05:00.320
SAPInst calls the LogInquirer. The output of the LogInquirer can be found in file sapinst_loginquirer.log.
TRACE 2015-03-25 11:05:06.122 [iaxxgenimp.cpp:638]
CGuiEngineImp::showMessageBox()
<html> <head> </head> <body> <p> An error occurred while processing option <i>SAP Enhancement Package 1 for SAP N
etWeaver 7.3 > SAP ASE > System Copy > Target System > Standard System > Based on AS ABAP > Database Refresh or M
ove( Last error reported by the step: Assertion failed: Unable to load database <SID>.)</i>. You can now: </p> <ul>
<li> Choose <i>Retry</i><br>to repeat the current step. </li> <li> Choose <i>Log Files</i><br>to get more inform
ation about the error. </li> <li> Stop the option and continue later. </li> </ul> <p> Log files are written to /t
mp/sapinst_instdir/NW731/SYB/COPY/SYSTEM/STD/AS-ABAP/REF. </p> </body></html>
TRACE 2015-03-25 11:05:06.124 [iaxxgenimp.cpp:1031]
CGuiEngineImp::acceptAnswerForBlockingRequest
Waiting for an answer from GUI
In sapinst.log I found this:
ERROR 2015-03-25 11:04:59.573
FCO-00011 The step syb_step_setup_preload with step key |NW_ABAP_DB_DBRefresh|ind|ind|ind|ind|0|0|NW_ABAP_DB|ind
|ind|ind|ind|0|0|NW_CreateDBandLoad|ind|ind|ind|ind|createdbandload|0|NW_CreateDB|ind|ind|ind|ind|createdb|0|NW_S
YB_DB|ind|ind|ind|ind|SYB_DB_CONTEXT|0|syb_step_setup_preload was executed with status ERROR ( Last error reporte
d by the step: Assertion failed: Unable to load database <SID>.).
INFO 2015-03-25 11:04:59.772
Creating file /tmp/sapinst_instdir/NW731/SYB/COPY/SYSTEM/STD/AS-ABAP/REF/__instana_tmp.xml.
INFO 2015-03-25 11:05:00.307
Removed file /tmp/sapinst_instdir/NW731/SYB/COPY/SYSTEM/STD/AS-ABAP/REF/instslana.xml.
INFO 2015-03-25 11:05:00.308
Creating file /tmp/sapinst_instdir/NW731/SYB/COPY/SYSTEM/STD/AS-ABAP/REF/instslana.xml.Hello Kiran,
I did a few tests again yesterday, and it was really a stupid mistake from myside.
The error message did mean, that there wasn't enough space.
It isn't the authority issue, it was a leak of space.
FYI, the complete DB-Size of Source System is required - NOT JUST RESERVED SPACE!!!
Thx for help and sorry for stealing your time :O -
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 -
Activating data in DSO got dump SAPSQL_EMPTY_TABNAME after BW system copy
Hi all,
We had an issue after system copy.
After a system copy the data in the standard DSOs(all of them) cannot be activated. The DOSs themselves are active, the transformations are active but if one attempts to load data and activate u2013 it does not work. The job terminates with shortdump SAPSQL_EMPTY_TABNAME.
Found the issue is caused by u201Cmore than one versionu201D of the change log.
We tried the Program RSAR_RSTSODS_CHANGELOG_VRS but it didn't work.
We had the solution like this:
After activating the DSO itself(the object) using RSDG_ODSO_ACTIVATE the issue disappears and the data can be activated. Issue also disappears. BUT Drawback: Activating the DSO causes the transformations to deactivate.Then we used the program RSDG_TRFN_ACTIVATE to activate all transformations. And then the issue disappeared.
Want to know what the root cause for this. From some SDN threads, mentioned BDLS job in the post refresh steps are not correctly done during system copy may cause this issue. How did the BDLS run wrongly cause this issue? And what is the exact correct way? We ran BDLS for each source systems inlcuding the target refreshed BW system itself by the default selection - conversion of Client-Dependent and Client-Independent Tables; because we used database copy
for the system refresh.
We also restored all source systems in RSA1 inlcuding the refreshed BW system own in the post-refresh steps.
Thank you very much for your information and suggestion.
HemingHi Arun, as you say two change log tables it´s strange. In fact in my opinion it´s not right but the problem is that the second change log table appears after executing std SAP report RSDG_ODSO_ACTIVATE in order to be able to activate the DSO. So the solution provided by SAP it works but i´m not sure if the right one. Besides this the original change log table is full of data while the second one is empty... for new loads which are gonna a be filled by the activation process ? I suppose the second one... will this have some impact with the data stored in the first one... not in theory but.... i do not feel confortable with the consequences of this report.
And the most important, it seems that the reason why the DSO and the change log table had problems is due to a some problems or missing steps after executing the BDLS after BW system refresh but nobody can confirm this point...
So, i´ve been able to solve the issue but now i have two change log tables for the same DSO.
Anybody has the same situation after executing the above mentioned SAP std report ?
Regards,
Joaquin Casas Baca-Castex -
PI 7.11 sp6 system copy causes target sys to register with source
Experts,
We have a PI 7.1 (EHP1, sp6) PI system based on AIX 6.1 OS and Oracle 11g.
I recently did the standard PI system copy from a prod source (PIP) to a training target (PIT).
I used the most recenty PI system copy guide that is specific for PI 7.1 EHP1
I did not run into any major problems doing the steps of the itself.
I did the usual "post" steps, documented in the guide that really are done on any NW system.
Then I got into the specific "PI" post steps and that's where I now have a problem.
I could not run the "wizard for post copy" since I'm on 7.11sp6. Yes, I know they "downported" it but I don't have those latest LMtools type packages. Anyway, I'm OK with that.
I followed all the steps, fixing my RFCs, JCos, Destinations, cleaning up SLD, SLDAPICUST, creating new business systems...etc.
My big problem is with the exchange profile. Yes, it's easy to change all the SIDs and hostnames using the search tool for all the parameters in the exchange profile, but the one I COULD NOT CHANGE was the "ABAP Connection". In there right after the copy was the hostname of the prod system, the client, and the user PILDUSER. I attempted to put the hostname of my target (PIT) system, but I would get the error:
RFC 399 unable to connect
I'm certain the user is NOT locked and the password is correct for PILDUSER.
Worse yet, If I left the hostname in there that was set to "prod", then when I changed all the other values in the "parameters" section of the XI profile, then it actually changed my PROD system!!
If I keep the ABAP connection to PIT, then the entire exchange profile disappears for PIT.
Also, now my PROD system shows the PIT system as a "non-central adapter engine".
Ughh! I'm totally stuck. I'm not sure what to do.
It's as if the PIT (PI training) system somehow is linked to PIP (PI prod). It's like PIT doesn't think he is his own box...
Any ideas? I'm resisting opening a message because this will be so hard to explain to sap support.
--NICKHi Nick,
We went thru the same issue. Fortunately, it was between Dev to sandbox. I stopped the dev system and changed the exchange profile parameters to sandbox hostname and brought the Dev up to fix the issue.
Prod showing as Non-Central Adapter engine :- Check your Business System in SLD and In CIM Instances in SLD, check your XI Integration server assigned to right Business System.
Note 764176 - Error in XI due to inconsistent SLD contents :- helped me come over PI post step issues.
Thanks,
Arjun -
PI 7.11 sp6 system copy Exchange Profile error code: 399
Experts,
We have a PI 7.1 (EHP1, sp6) PI system based on AIX 6.1 OS and Oracle 11g.
I recently did the standard PI system copy from a prod source (PIP) to a training target (PIT).
I used the most recenty PI system copy guide that is specific for PI 7.1 EHP1
I did not run into any major problems doing the steps of the copy itself.
I did the usual "post" steps, documented in the guide that really are done on any NW system.
Then I got into the specific "PI" post steps and that's where I now have a problem.
I followed all the steps, fixing my RFCs, JCos, Destinations, cleaning up SLD, SLDAPICUST, creating new business systems...etc.
My big problem is with the exchange profile. Yes, it's easy to change all the SIDs and hostnames using the search tool for all the parameters in the exchange profile, but the one I COULD NOT CHANGE was the "ABAP Connection". In there right after the copy was the hostname of the prod system, the client, and the user PILDUSER. I attempted to put the hostname of my target (PIT) system, but I would get the error:
com.sap.rprof.dbprofiles.DBException: RFC call returned an error code: 399
I'm certain the user is NOT locked and the password is correct for PILDUSER. It'll give me a different error if I put the wrong password in, so I know it's hitting my system.
Worse yet, If I left the hostname in there that was set to "prod", then when I changed all the other values in the "parameters" section of the XI profile, then it actually changed my PROD system!!
If I keep the ABAP connection to PIT, then the entire exchange profile disappears for PIT.
I see these errors in the default trace and application log:
Caused by: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_NOT_FOUND:
No such instance: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",
Name="PIT.SystemHome.<traininghostname>"
Caused by: com.sap.lcr.api.cimclient.LcrException: CIM_ERR_NOT_FOUND: No such instance: SAP_J2EEEngineCluster.CreationClassName="SAP_J2EEEngineCluster",Name="PIT.SystemHome.<traininghostname>"
at com.sap.lcr.api.cimclient.SimpleResponseAnalyser.raiseExceptionOnError(SimpleResponseAnalyser.java:120)
#2.#2011 11 03 13:49:47:008#0-500#Error#com.sap.aii.af.service.sld.SLDRegistrationJob#
#BC-XI-CON-AFW#com.sap.aii.af.lib#7E3832DEA80F002B00000000008700C6#4804850000001902##com.sap.aii.af.service.sld.SLDRegistrationJob.SLDRegistrationJob.invoke()#J2EE_GUEST#0##0AFD01D4064C11E1CB5E7E3832DEA80F#0afd01d4064c11e1cb5e7e3832dea80f#0afd01d4064c11e1cb5e7e3832dea80f#0#Application [24]#Plain##
SLD Registration Job: No access to SLD. Waiting for next retry. Error: com.sap.aii.af.lib.sld.SLDException: Failed to initialize ExchangeProfile properties. Reason: Unable to read configuration data (ExchangeProfile/aii.properties)#
#2.#2011 11 03 14:51:18:096#0-500#Error#com.sap.esi.esp.service.server.ESPServiceInterfaceAbstract#
#BC-ESI-WS-JAV#tcesiespsrv#7E3832DEA80F001100000000009A004C#4804850000001385##com.sap.esi.esp.service.server.ESPServiceInterfaceAbstract####109F6812065511E1BF9C7E3832DEA80F#109f6812065511e1bf9c7e3832dea80f#109f6812065511e1bf9c7e3832dea80f#0#Service Runner [tcesiespsrv]#Plain##
+There is problem reading the hostname from the ClusterManager. This could lead to improper wsdl links.#
SLDCHECK shows this:
Function call returned exception code 3
Access to the XI Profile is currently disrupted.
I can't be the first person to run into this.
SO strange that I can actually plug in either my dev/QA or PROD hostname in the "ABAP connection" box and it WILL ACCEPT IT...but then, it registered my training system as a "non central adapter engine". I don't want that.
Any ideas?
Another issue is that the SLD PI information from the PIT system is missing the "Integration Directory". It has the other 5 entries...Adapter Engine, Domain, Integration Repository, Integration Server, RWB.
Thanks for reading this,
NICKHere is the error I get when I try to change the "abap connection" to the correct hostname:
RFC call returned an error code: 399
Stack Trace class com.sap.rprof.dbprofiles.DBException:<br><pre>at com.sap.rprof.dbprofiles.DBProfiles.checkReturn(DBProfiles.java:184) at com.sap.rprof.dbprofiles.DBProfiles.getProfile(DBProfiles.java:105) at com.sap.rprof.dbprofiles.RemoteProfile.readRemoteProfileFromMedia(RemoteProfile.java:1378) at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfileFromFactory(RemoteProfile.java:204) at com.sap.rprof.dbprofiles.RemoteProfile.getRemoteProfile(RemoteProfile.java:154) at com.sap.rprof.dbprofiles.ExchangeProfile.getExchangeProfile(ExchangeProfile.java:46) at com.sap.rprof.remoteProfile.webui.ProfileWebTree.<init>(ProfileWebTree.java:24) at com.sap.rprof.remoteProfile.webui.Edit.getWebTree(Edit.java:322) at JEE_jsp_treeexprof_4804850_1319481176000_1319565151782._jspService(JEE_jsp_treeexprof_4804850_1319481176000_1319565151782.java:59) at com.sap.engine.services.servlets_jsp.lib.jspruntime.JspBase.service(JspBase.java:102) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140) at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:436) at com.sap.engine.services.servlets_jsp.server.servlet.JSPServlet.service(JSPServlet.java:240) at javax.servlet.http.HttpServlet.service(HttpServlet.java:847) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:140) at com.sap.engine.services.servlets_jsp.server.Invokable.invoke(Invokable.java:37) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.runServlet(HttpHandlerImpl.java:493) at com.sap.engine.services.servlets_jsp.server.HttpHandlerImpl.handleRequest(HttpHandlerImpl.java:298) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:399) at com.sap.engine.services.httpserver.server.RequestAnalizer.startServlet(RequestAnalizer.java:388) at com.sap.engine.services.servlets_jsp.filters.DSRWebContainerFilter.process(DSRWebContainerFilter.java:48) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ServletSelector.process(ServletSelector.java:84) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.servlets_jsp.filters.ApplicationSelector.process(ApplicationSelector.java:244) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.WebContainerInvoker.process(WebContainerInvoker.java:78) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.ResponseLogWriter.process(ResponseLogWriter.java:60) at com.sap.engine.services.httpserver.chain.HostFilter.process(HostFilter.java:9) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.DefineHostFilter.process(DefineHostFilter.java:27) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.MonitoringFilter.process(MonitoringFilter.java:29) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.MemoryStatisticFilter.process(MemoryStatisticFilter.java:43) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.filters.DSRHttpFilter.process(DSRHttpFilter.java:42) at com.sap.engine.services.httpserver.chain.ServerFilter.process(ServerFilter.java:12) at com.sap.engine.services.httpserver.chain.AbstractChain.process(AbstractChain.java:78) at com.sap.engine.services.httpserver.server.Processor.chainedRequest(Processor.java:428) at com.sap.engine.services.httpserver.server.Processor$FCAProcessorThread.process(Processor.java:247) at com.sap.engine.services.httpserver.server.rcm.RequestProcessorThread.run(RequestProcessorThread.java:45) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:122) at com.sap.engine.core.thread.execution.Executable.run(Executable.java:101) at com.sap.engine.core.thread.execution.CentralExecutor$SingleThread.run(CentralExecutor.java:327) </pre> -
Unable to log in to portal after system copy
Good day
I have copied my production portal system to a test system. I am using an ECC Abap system as my user store. The portal start successfully and I am able to access the Visual administrator.
I am however unable to log on to the portal. The error I get is "User authentication error".
Below is an extract from the security log:
#1.5#0011259C05FB0054000002F500001B9800043F56F6157AED#1195542635224#/System/Security/Authentication#sap.com/irj#com.sap.engine.services.security.authentication.logincontext#Guest#0##sapsep.sap.lonmin_SEP_32623050#Guest#af93b280973711dc980a0011259c05fb#SAPEngine_Application_Thread[impl:3]_35##0#0#Error#1#com.sap.engine.services.security.authentication.logincontext#Plain###LOGIN.FAILED
User: N/A
Authentication Stack: ticket
Login Module Flag Initialize Login Commit Abort Details
com.sap.security.core.server.jaas.EvaluateTicketLoginModule SUFFICIENT ok false false true
com.sap.security.core.server.jaas.CreateTicketLoginModule SUFFICIENT ok false false true
com.sap.engine.services.security.server.jaas.BasicPasswordLoginModule REQUISITE ok true true true
com.sap.security.core.server.jaas.CreateTicketLoginModule REQUISITE ok true exception true null#
#1.5#0011259C05FB0054000002F700001B9800043F56F61580BC#1195542635240#/System/Security/Audit#sap.com/irj#com.sap.security.core.util.SecurityAudit#Guest#0##sapsep.sap.lonmin_SEP_32623050#Guest#af93b280973711dc980a0011259c05fb#SAPEngine_Application_Thread[impl:3]_35##0#0#Warning#1#com.sap.security.core.util.SecurityAudit#Plain###Guest | LOGIN.ERROR | null | | Login Method=[default], UserID=[oostw], IP Address=[172.27.2.137], Reason=[Access Denied.]#
Please can someone assist.
Thanks
WilhelmHello!
It looks like your system is configured for ticket authentication. As you did a system copy the SSO-ticket might not be working anymore. If this is the case you need fix the SSO or you need to re-configure your Portal (at least temporarily) to allow other authentication methods (like basic password authentication).
You can configure the order of the authentication methods in VisualAdmin and set the 'levels' (Required/Sufficient/etc.) there as well.
Hope this helps,
Jörg -
Dear All,
Good Day
We are doing a BI Quality System Refresh from our BI Production System.
we are on Windows 2003 R2 Server & Database MS SQL 2005 Server.
We followed the Standard System Copy / Migration (Load Based) Installation method.
We finished the SAP installation positively up to the 13th Phase, while in the "IMPORT ABAP Phase" we are getting the following errors.
Loading of 'SAPSLOAD' import package: OK
Import Monitor jobs: running 0, waiting 5, completed 102, failed 10, total 117.
Import Monitor jobs: running 1, waiting 4, completed 102, failed 10, total 117.
Import Monitor jobs: running 2, waiting 3, completed 102, failed 10, total 117.
Import Monitor jobs: running 3, waiting 2, completed 102, failed 10, total 117.
Loading of 'SAPUSER' import package: OK
Import Monitor jobs: running 2, waiting 2, completed 103, failed 10, total 117.
Loading of 'SAPDODS_13' import package: OK
Import Monitor jobs: running 1, waiting 2, completed 104, failed 10, total 117.
Loading of 'SAPDODS_6' import package: OK
Import Monitor jobs: running 0, waiting 2, completed 105, failed 10, total 117.
Import Monitor jobs: running 1, waiting 1, completed 105, failed 10, total 117.
Loading of 'SAP0000' import package: OK
Import Monitor jobs: running 0, waiting 1, completed 106, failed 10, total 117.
TRACE 2011-05-01 11:58:56.355
Function setMessageIdOfExceptionMessage: nw.programError
WARNING[E] 2011-05-01 11:58:56.355
CJSlibModule::writeError_impl()
CJS-30022 Program 'Migration Monitor' exits with error code 103. For details see log file(s) import_monitor.java.log, import_monitor.log.
TRACE 2011-05-01 11:58:56.433 [iaxxejsbas.hpp:483]
EJS_Base::dispatchFunctionCall()
JS Callback has thrown unknown exception. Rethrowing.
ERROR 2011-05-01 11:58:56.480 [sixxcstepexecute.cpp:950]
FCO-00011 The step runMigrationMonitor with step key |NW_ABAP_OneHost|ind|ind|ind|ind|0|0|NW_Onehost_System|ind|ind|ind|ind|1|0|NW_CreateDBandLoad|ind|ind|ind|ind|10|0|NW_ABAP_Import_Dialog|ind|ind|ind|ind|5|0|NW_ABAP_Import|ind|ind|ind|ind|0|0|runMigrationMonitor was executed with status ERROR .
TRACE 2011-05-01 11:58:56.527 [iaxxgenimp.cpp:752]
CGuiEngineImp::showMessageBox
<html> <head> </head> <body> <p> An error occurred while processing option SAP NetWeaver 7.0 including Enhancement Package 1 Support Release 1 > Software Life-Cycle Options > System Copy > MS SQL Server > Target System Installation > Central System > Based on AS ABAP > Central System. You can now: </p> <ul> <li> Choose <i>Retry</i> to repeat the current step. </li> <li> Choose <i>View Log</i> to get more information about the error. </li> <li> Stop the option and continue with it later. </li> </ul> <p> Log files are written to C:\Program Files/sapinst_instdir/NW701/LM/COPY/MSS/SYSTEM/CENTRAL/AS-ABAP/. </p> </body></html>
TRACE 2011-05-01 11:58:56.527 [iaxxgenimp.cpp:1255]
CGuiEngineImp::acceptAnswerForBlockingRequest
Waiting for an answer from GUI
*" In The importmonitor log "*_
INFO: 2011-05-01 11:57:57 com.sap.inst.migmon.LoadTask run
Loading of 'SAPDODS_6' import package is successfully completed.
TRACE: 2011-05-01 11:58:26 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is started.
TRACE: 2011-05-01 11:58:26 com.sap.inst.migmon.LoadTask processPackage
Task file generation for 'SAP0000' import package:
K:\usr\sap\FBQ\SYS\exe\uc\NTAMD64\R3load.exe -ctf I E:\Backup\ABAP\DATA\SAP0000.STR "C:\Program Files\sapinst_instdir\NW701\LM\COPY\MSS\SYSTEM\CENTRAL\AS-ABAP\DDLMSS.TPL" SAP0000.TSK MSS -l SAP0000.log -o D
TRACE: 2011-05-01 11:58:26 com.sap.inst.migmon.LoadTask processPackage
Loading of 'SAP0000' import package into database:
K:\usr\sap\FBQ\SYS\exe\uc\NTAMD64\R3load.exe -i SAP0000.cmd -dbcodepage 4103 -l SAP0000.log -loadprocedure fast
INFO: 2011-05-01 11:58:26 com.sap.inst.migmon.LoadTask run
Loading of 'SAP0000' import package is successfully completed.
WARNING: 2011-05-01 11:58:56
Cannot start import of packages with views because not all import packages with tables are loaded successfully.
WARNING: 2011-05-01 11:58:56
10 error(s) during processing of packages.
INFO: 2011-05-01 11:58:56
Import Monitor is stopped.
Kindly Do the needful.
Thanks in Advance.
Regards,
DeepakDid you execute the report SMIGR_CREATE_DDL on the source system and copied the resulting SQL files to the database dump directory?
Markus
Maybe you are looking for
-
QT in html, events fired and movie internals doc
Hi, The Javascript Scripting Guide says under "Executing JavaScript Functions From QuickTime", page 11: Wired actions can be triggered by user interaction, as a result of a frame in the movie being displayed, or as the result of arbitrary wired calcu
-
Sort more sine periods in one period
Hi everyone. I would like to sort more periods of sine waves into just one. I'm having problem with programming it. I've attached .vi wich does not work correctly. Help, please. Attachments: Sort To One Period.vi 33 KB
-
When trying to print an open PDF doc, created from InDesignCC, a box appears asking to PRINT To File, and asks to save already saved doc. Once hit save, anyway, the program then does not respond. I can print if I close the open doc and access it from
-
How to change commodity Code for material grp in certain plant
Hi, I would like to change commodity code for some material group under certain plant May I know how to do this. I went to the following SPRO path, however, the table does not mention the plant and the material group for me to change. SD>Foreign Trad
-
Problem showing remote systems in MAX
I am having trouble viewing traces set up on remote systems in Max. I am using version 4.7.0f4 Whenever I try to set up a new remote system, it cannot find any remote computers. I have tried using both the computer name (which is resolved to an IP