BI 4.1 with MaxDB 7.8
Are there any experiences with BI 4.1 running on MaxDB 7.8 or 7.9 ?
According to the PAM only MaxDB 7.7 is supported !
Hello,
Unfortuanetlly, Max DB 7.8 and 7.9 are not officially supported for the BI platform.
Regards,
Insaf
Similar Messages
-
Using Entry&Approval with MAXDB database
Hi all,
I'm trying to use the Entry&Approval module of SSM, but I'm getting into some problems that maybe someone can help me. I'm using SSM7.5 SP6 with MAXDB as my system database.
I already create my PAS database, I create the metric sets, I put some data there, but when I try to load the data into PAS database I get this error in the trace file:
LSS>
LSS> ... WFMDE_SETUP.PRO FOR MAXDB
LSS>
LSS> output REVIEW_LOAD;SAMPLE over
LSS> echo LOADSTARTED
LOADSTARTED
LSS> output off
LSS>
LSS> checkpoint update
LSS> checkpoint freeze
LSS>
LSS> set control WFMDELINK SSM_CB_EA
LSS>
LSS> access lslink
LSLink> connect SSM_CB_EA
LSLink>
LSLink> ... clear the scorecard status table
LSLink> begin
> DELETE FROM CPMS_SCORE_STATUS
> WHERE CPMS_CONTEXT_ID IN (SELECT ID FROM CPMS_CONTEXT
> WHERE CONTEXT_NAME IN (SELECT CONTEXT FROM CPMS_PASUSER
> WHERE UPPER(USEDB) = UPPER('SAMPLE')))
> end
[SAP AG][SQLOD32 DLL][SAP DB] Base table not found;-4004 POS(13) Unknown table name:CPMS_SCORE_STATUS
SQLSTATE: S0002
SQL System code: -4004
LSLink>
LSLink> ... create the LOADALL proc that will run wfmde_load.pro once for each content set
LSLink> begin
> SELECT DISTINCT CPMS_EA_MASTER_ID
> FROM CPMS_EA_DETAIL
> WHERE ID IN
> (
> SELECT DISTINCT CPMS_EA_DETAIL_ID
> FROM CPMS_EA_DATA, CPMS_EA_CUBES
> WHERE CPMS_EA_DATA.CPMS_EA_CUBES_ID = CPMS_EA_CUBES.ID
> AND UPPER(CUBE_NAME) = 'SAMPLE'
> )
> end
[SAP AG][SQLOD32 DLL][SAP DB] Base table not found;-4004 POS(108) Unknown table name:CPMS_EA_DATA
SQLSTATE: S0002
SQL System code: -4004
LSLink>
+LSLink> lss create code = "job 'wfmde_load.pro' '" + CPMS_EA_MASTER_ID + "'"+
LSLink> output proc LOADALL;PIPADMINDEFAULT
LSLink> peek create nohead nonumb
No Fields currently Selected
ACC004:
No Record Has Been Accessed From the Database.
ACC004:
No Record Has Been Accessed From the Database.
CHE FRE
CHE UPD
In PAS I create the linkid ssm_cb_ea pointing to DB3 MAXDB database. I also try for the MAXDB1 database, but the same result
[http://img713.imageshack.us/img713/8611/72008201.jpg]
Looks like some tables are missing !?!?!? Did I do any mistake?
Thanks in advance for all the help
PedroHi Bob,
thanks for your answer.
I believe that in the LSSERVER.ini all the information is correct, because PAS is working fine, except the selects to the MAXDB database. Here it is the LSSERVER.INI
[Windows]
DEFAULTMEMORY=1200000
DBHOME=C:\Program Files (x86)\SAP BusinessObjects\Strategy Management\ApplicationServer\HOME
PAGEDB=C:\Program Files (x86)\SAP BusinessObjects\Strategy Management\ApplicationServer\HOME\PAGEDB
MASTERDB=C:\Program Files (x86)\SAP BusinessObjects\Strategy Management\ApplicationServer\DATA\MASTERDB
LOCKFILE=C:\Program Files (x86)\SAP BusinessObjects\Strategy Management\ApplicationServer\DATA\LSSLOCK
JUICE=C:\Program Files (x86)\SAP BusinessObjects\Strategy Management\ApplicationServer\DATA\JUICE.ENG
TBDB=C:\Program Files (x86)\SAP BusinessObjects\Strategy Management\ApplicationServer\DATA\TBDB.ENG
APLIB=C:\Program Files (x86)\SAP BusinessObjects\Strategy Management\ApplicationServer\DATA\APLIB
LIBDB=C:\Program Files (x86)\SAP BusinessObjects\Strategy Management\ApplicationServer\DATA\APLIB
CGLIB=C:\Program Files (x86)\SAP BusinessObjects\Strategy Management\ApplicationServer\DATA\CGLIB
SMREPORT=C:\Program Files (x86)\SAP BusinessObjects\Strategy Management\ApplicationServer\DATA\SMREPORT
INITIAL=C:\Program Files (x86)\SAP BusinessObjects\Strategy Management\ApplicationServer\DATA\INITIAL
DBPATH=C:\Program Files (x86)\SAP BusinessObjects\Strategy Management\InternetPub\Procs;C:\Program Files (x86)\SAP BusinessObjects\Strategy Management\ApplicationServer\HOME;C:\Program Files (x86)\SAP BusinessObjects\Strategy Management\ApplicationServer\DATA
VERSION=940
EDITFULLSCREEN=0
EDITWINXPOS=0
EDITWINYPOS=0
EDITWINWIDTH=0
EDITWINHEIGHT=0
[Server]
SERVERPATH=C:\Program Files (x86)\SAP BusinessObjects\Strategy Management\ApplicationServer
[localhost]
tcp_protocol=winsock
username=pipadmin
password=?
PROTOCOL=TCP
SERVICE=PILOT
CURSOR=LSSCMPTR
And when I said changing between DB's I was meaning the two MAXDB databases that exist on my system. I assume that the E&A stuff is stored in the DB3 (in my case) MAXDB database, no? I just test against the MAXDB1 database to be sure that I was not pointing to the wrong database. And because both are MAXDB databases, the proc's are the same.
Pedro -
SQL Case Statement Problem with Maxdb
Hello,
I'm running a J2E application on Netweaver AS. I have on problem that I just cannot figure out.
The statement works in SQL Studio but when I try to code it it does not work at all.
select COLA, SUM(CASE WHEN COLB=10 THEN 1 ELSE 0 END) from TABLE group by COLA
When executed as statement in Java I get:
Error [javax.servlet.ServletException: java.lang.IllegalStateException: illegal stack size: 4
contents:
com.sap.sql.tree.SelectStatement
com.sap.sql.tree.IntegerLiteral
com.sap.sql.tree.IntegerLiteral
com.sap.sql.tree.ComparisonPredicate], with root cause [java.lang.Exception: java.lang.IllegalStateException: illegal stack size: 4
contents:
com.sap.sql.tree.SelectStatement
com.sap.sql.tree.IntegerLiteral
com.sap.sql.tree.IntegerLiteral
com.sap.sql.tree.ComparisonPredicate].
Any thoughts on that? Thanks!
Edited by: MD on Feb 18, 2009 7:37 PMHi MD,
with SQL Studio you mean you work with MaxDB?
Are you sure you're working directly on MaxDB and not with OpenSQL? (That's different!)
If you want the first, try setting SQL type "vendor" or "native sql". In such case you have to define a new custom datasource through configuration. How that works depends on the version you are using.
Try to find out what the actual error message is. The stack trace is not enough. There should be more.
Regards,
Benny -
How to change SID on a SAP System with Maxdb ?
Hello,
I've tryed to migrate /clone a productive system from physical to virtual for testing, and it went OK.
Now, i've done the same to another physical machine and SAP 4.6C r3 goes up,as well as the database MaxDB 7.5 on the new machine.
but now i have two problems:
First, the license key: i have to request a new one. i believe that i can do it using https://websmp110.sap-ag.de/licensekey
Second: the SID is the same, as i have clone the system from one side to another. Same OS, same kernel, etc etc etc.
In order to achieve the possibility to transform the new cloned system in a DEV system for my SAP landscape, i must rename the <sid> of my SAP.
I've changed already the SAPSYSTEMNAME = PRD to SAPSYSTEMNAME = DEV, created a new user like "devadm" renamed the directories where i could find "prd" to "dev" and even in the /home/<sid>adm files i've changed everything from PRD to DEV.
However, this have not worked for me. As that did not worked out, made the "cloning" again. And now i' again with the problem of entering the new license key ( i believe i can request it via that webpage mention above) and changing the <sid> of the system.
Is there any sap not where i can see how to change the <sid> / SAPSYSTEMNAME ?
Thank you
my system is a RHEL5 with MaxDB 7.5 64 bits
FilipeHi Filipe,
afaik the SID of a SAP instance cannot be changed later on.
But this is not a db-topic - so you're basically asking the wrong people here in the forum.
Perhabs is more suited for this question.
Concerning the licensekey : yes, you will need a new one if you change the hardware or db platform.
KR Lars -
Replication / synchronization with MaxDB using Windows
Hi,
is there somewhere a tutorial how to use replication / synchronization with MaxDB using Windows?
I found information about the Synchronization Manager but it seems that it's no more available for Download.
The Database Studio description points out that it will be useable for MaxDB 7.7 and upper versions,
but I can't also find V7.7 anywhere for download...
So do I need and where can I get it?
Thanks,
AndreHi Wolgang,
thanks for your support - this is the output:
C:\Program Files\sapdb\indep_prog\bin>Exception in thread "main" java.lang.Unsat
isfiedLinkError: no swt-win32-2128 in java.library.path
at java.lang.ClassLoader.loadLibrary(Unknown Source)
at java.lang.Runtime.loadLibrary0(Unknown Source)
at java.lang.System.loadLibrary(Unknown Source)
at org.eclipse.swt.internal.Library.loadLibrary(Library.java:104)
at org.eclipse.swt.internal.win32.OS.<clinit>(OS.java:42)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Unknown Source)
at org.eclipse.swt.internal.Library.getPlatform(Library.java:49)
at org.eclipse.swt.internal.Library.loadLibrary(Library.java:83)
at org.eclipse.swt.internal.Callback.<clinit>(Callback.java:31)
at org.eclipse.swt.SWT.getPlatform(SWT.java:2227)
at org.eclipse.swt.SWT.<clinit>(SWT.java:2368)
at org.eclipse.jface.action.ActionContributionItem.<clinit>(ActionContri
butionItem.java:60)
at org.eclipse.jface.action.ContributionManager.insertAfter(Contribution
Manager.java:268)
at com.sap.sdb.syncMan.gui.SyncManGUI.drawMSG_LRU(SyncManGUI.java:1422)
at com.sap.sdb.syncMan.gui.SyncManGUI.createMenuManager(SyncManGUI.java:
428)
at org.eclipse.jface.window.ApplicationWindow.addMenuBar(ApplicationWind
ow.java:223)
at com.sap.sdb.syncMan.gui.SyncManGUI.<init>(SyncManGUI.java:230)
at com.sap.sdb.syncMan.gui.SyncManGUI.main(SyncManGUI.java:821)
Thanks,
Andre -
Hi All,
we can configured dr server with oracle in this way very easily.
1) install sap on target system (DR)
2) copy offline data file oracle control files and redolog files from source
3)past at same location of target (DR)
4) start mount db
5) recover db using backup control file.
auto
Please guide how we configure DR with maxdb, in this way or there is an other way.
Best Regards
KhanHi Imran,
Please follow in given sequence.
dbmcli -u <MaxDB User>,<Its password> -d <DB SID>
To bring Database in admin mode
dbmcli prompt>db_admin -f
dbmcli prompt>util_connect
To start resoration of Datafile
dbmcli prompt>db_activate RECOVER <media name> DATA
##Use the media name which you have defined with complete path of Data backup location
Import the first log backup
dbmcli prmot>recover_start <log Media name> LOG 976
##use the media name which you have defined with complete path of Log backup location, where log file names were like XYZ_log.976
Import any more log backups, provide full pathname as well.
dbmcli prompt>recover_replace <log Media name> /sapdb/BACKUP/tempLogRestore/XYZ_log 977
When all logs are restored
dbmcli prmot>recover_ignore
To bring Database online
dbmcli prmot>db_online
Hope this helps. -
Changing saplog directory with maxdb
Hi,
I have installed 04s portal server with maxdb in my desktop. I specified, all directories to point to D: during installation. However, saplog directory alone got created in C drive.
It is occupying so much space, that am effectively not able to use my server.
I have specified overwrite mode for log area.
How do i change the saplog directory to point to D drive. Or will deleting the DISKL001 file cause any issues using my portal server. If i manually create a similar structure in my d drive and copy the DISKL001 file, where should i change to reflect the new location of saplog directory?
Thanks
Best Regards
SumathiHi,
In Log Settings of Configuration tab, there is no option to change the directory where DISK001 is stored. All i can see is three radio options to set Log Mode, Overwrite mode and Activate or Deactivate the Redo Log Management.
Version of Maxdb manager is 7.6
Any other option to change the directory
Thanks
Best Regards
Sumathi -
Trouble with instalation of NW2004s with maxDB - no cluster
I do new installation on SUSE 9.0 with maxdb and j2sdk1.4.2_13
My problem is, that I can not pass thought step 42 of 50 because of error in callSdmViaSapinst.log:
Nov 21, 2006 12:42:58... Info: Start logging to console
Nov 21, 2006 12:42:58... Info:
Nov 21, 2006 12:42:58... Info: ============================================
Nov 21, 2006 12:42:58... Info: = Starting to execute command 'deploy' =
Nov 21, 2006 12:42:58... Info: ============================================
Nov 21, 2006 12:42:58... Info: Starting SDM - Software Deployment Manager...
Nov 21, 2006 12:42:58... Info: tc/SL/SDM/SDM/sap.com/SAP AG/7.0006.20060303095356.0000
Nov 21, 2006 12:43:00... Info: SDM operation mode successfully set to: Standalone
Nov 21, 2006 12:43:00... Info: Initializing Network Manager (54817)
Nov 21, 2006 12:43:00... Info: Checking if another SDM is running on port 54818
Nov 21, 2006 12:43:00... Info: -------------------------- Starting deployment ------------------------
Nov 21, 2006 12:43:00... Info: Error handling strategy: OnErrorStop
Nov 21, 2006 12:43:00... Info: Prerequisite error handling strategy: OnPrerequisiteErrorStop
Nov 21, 2006 12:43:00... Info: Update strategy: UpdateLowerVersions
Nov 21, 2006 12:43:00... Info: Starting deployment prerequisites:
Nov 21, 2006 12:43:01... Info: Loading selected archives...
Nov 21, 2006 12:43:01... Info: Loading archive '/install/java/NW_2004s_SR1Java_based_SW_Comp/J2EE_OSINDEP/UT/EPBC06_0.SCA'
Nov 21, 2006 12:43:01... Info: Selected archives successfully loaded.
Nov 21, 2006 12:43:02... Info: Actions per selected component:
Nov 21, 2006 12:43:02... Info: Initial deployment: Selected development component 'irj'/'sap.com'/'SAP AG'/'7.0006.20060301194
711.0000' will be deployed.
Nov 21, 2006 12:43:02... Info: No action: Selected development component 'com.sapportals.prt.bridge'/'sap.com'/'SAP AG'/'7.000
6.20060301194711.0000' will not update currently deployed development component 'com.sapportals.prt.bridge'/'sap.com'/'SAP AG'
/'7.0006.20060301194711.0000'.
Nov 21, 2006 12:43:02... Info: Initial deployment: Selected software component 'EPBC'/'sap.com'/'SAP AG'/'1000.7.00.6.0.200603
05011500' will be deployed.
Nov 21, 2006 12:43:02... Info: No action: Selected development component 'com.sap.pcd.dbschema'/'sap.com'/'SAP AG'/'7.0006.200
60301194711.0000' will not update currently deployed development component 'com.sap.pcd.dbschema'/'sap.com'/'SAP AG'/'7.0006.2
0060301194711.0000'.
Nov 21, 2006 12:43:02... Info: No action: Selected development component 'com.sapportals.prt.portalruntime'/'sap.com'/'SAP AG'
/'7.0006.20060301194711.0000' will not update currently deployed development component 'com.sapportals.prt.portalruntime'/'sap
.com'/'SAP AG'/'7.0006.20060301194711.0000'.
Nov 21, 2006 12:43:02... Info: Ending deployment prerequisites. All items are correct.
Nov 21, 2006 12:43:03... Info: Saved current Engine state.
Nov 21, 2006 12:43:03... Info: Starting: Initial deployment: Selected development component 'irj'/'sap.com'/'SAP AG'/'7.0006.2
0060301194711.0000' will be deployed.
Nov 21, 2006 12:43:03... Info: SDA to be deployed: /usr/sap/BWK/DVEBMGS48/SDM/root/origin/sap.com/irj/sap AG/7.0006.2006030119
4711.0000/epbcsda.ear
Nov 21, 2006 12:43:03... Info: Software type of SDA: J2EE
Nov 21, 2006 12:43:03... Info: ***** Begin of SAP J2EE Engine Deployment (J2EE Application) *****
Nov 21, 2006 12:43:03... Info: Starting cluster instance processes.
Nov 21, 2006 12:43:06... Info: Starting the instance JC_suse_BWK_48 running on host suse
Nov 21, 2006 12:43:06... Info: Starting the instance JC_suse_BWK_48 processes. The instance is running on host suse
Nov 21, 2006 12:43:06... Info: ***** End of SAP J2EE Engine Deployment (J2EE Application) *****
Nov 21, 2006 12:43:06... Error: Aborted: development component 'irj'/'sap.com'/'SAP AG'/'7.0006.20060301194711.0000':
SDM could not start the J2EE cluster on the host suse! The online deployment is terminated.
JStartupFramework could not start server process for the instance JC_suse_BWK_48 on the host suse
(message ID: com.sap.sdm.serverext.servertype.inqmy.extern.EngineJ2EE620OnlineDeployerImpl.performAction(DeploymentActionType
s).STARTUP_CLUSTER)
Nov 21, 2006 12:43:07... Info: J2EE Engine is in same state (online/offline) as it has been before this deployment process.
Nov 21, 2006 12:43:07... Info: ----------------------- Deployment was successful ---------------------
Nov 21, 2006 12:43:07... Info: Summarizing the deployment results:
Nov 21, 2006 12:43:07... Error: Admitted: /install/java/NW_2004s_SR1Java_based_SW_Comp/J2EE_OSINDEP/UT/EPBC06_0.SCA
Nov 21, 2006 12:43:07... Error: Processing error. Return code: 4
suse:
at /usr/sap/..../j2ee/cluster I've got only:
bootstrap
instance.properties
instance.properties.vmprop
I have no
dispatcher and
server0
What Can I do?? I can login with SAPgui, but looks like j2ee not start.
Please help or suggest what can I do?
Best RegardsUnfortunatelly it's not working
it was something like:
java:21 and it hanged up about 15hours ;-(
I saw that the problem is:
Exception in thread "main" java.lang.NoClassDefFoundError: com/sap/engine/offline/OfflineToolStart
when gui sapinstaller is in proges on very first steps, at shell it's wrote :
UTL.java.log
java version "1.4.2_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)
Java HotSpot(TM) Client VM (build 1.4.2_13-b06, mixed mode)
Exception in thread "main" java.lang.NoClassDefFoundError: com/sap/engine/offline/OfflineToolStart
what's wrong with:
WARNING 2006-11-22 12:15:07
Execution of the command "/usr/lib/j2sdk1.4.2_13/j2sdk1.4.2_13/bin/java -classpath /usr/sap/BWK/SYS/global/sltools/sharedlib/l
auncher.jar -showversion -Xmx256m com.sap.engine.offline.OfflineToolStart com.sap.sl.ut.manager.UtlMain /sapmnt/BWK/BWK/global
/security/lib/tools:/usr/sap/BWK/SYS/global/sltools/sharedlib/sap.com~sl.ut.infoprovider_lib.jar:/usr/sap/BWK/SYS/global/sltoo
ls/sharedlib/sap.com~sl.ut.manager.offline.jar:/usr/sap/BWK/SYS/global/sltools/sharedlib/antlr.jar:/usr/sap/BWK/SYS/global/slt
ools/sharedlib/exception.jar:/usr/sap/BWK/SYS/global/sltools/sharedlib/jddi.jar:/usr/sap/BWK/SYS/global/sltools/sharedlib/logg
ing.jar:/usr/sap/BWK/SYS/global/sltools/sharedlib/offlineconfiguration.jar:/usr/sap/BWK/SYS/global/sltools/sharedlib/opensqlst
a.jar:/usr/sap/BWK/SYS/global/sltools/sharedlib/tc_sec_secstorefs.jar:/usr/sap/BWK/SYS/global/sltools/sharedlib/sap.comtcsdt
cvlimpl.jar:/usr/sap/BWK/SYS/global/sltools/sharedlib/SDMutil.jar:/usr/sap/BWK/SYS/global/sltools/sharedlib/SLUtil.jar:/sapd
b/programs/runtime/jar/sapdbc.jar -activated -prod_name=NetWeaver -usage_name=AAS -usage_vendor=sap.com -log=UTL_activate_usag
es.log -action=true -sid=BWK -dsn=jdbc/pool/BWK -ssprops=/usr/sap/BWK/SYS/global/security/data/SecStore.properties -ssk=/usr/s
ap/BWK/SYS/global/security/data/SecStore.key" finished with return code 1. Output:
java version "1.4.2_13"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_13-b06)
Java HotSpot(TM) Client VM (build 1.4.2_13-b06, mixed mode)
Exception in thread "main" java.lang.NoClassDefFoundError: com/sap/engine/offline/OfflineToolStart
thanks in advanced for Your help... -
Hello MaxDB Fans,
is it possible to create a auditing with MaxDB? We are in a high security enviroment and we need looging all access to the databases. This should be traced in a file (User XY has drop a table with sqlcli or shutdown a instance with dbmcli)
Thanks for you answer.
MartinHello,
you could audit all DML comands using INSERT, UPDATE and DELETE triggers.
For auditing a shutdown you could use the DBM event dispatcher or check the log files of the database.
regards
Wolfgang -
Content Server 6.40 with MaxDB 7.7.4 giving ODBC State 00000 error
Hi Guru,
I'm having a problem with Content Server 6.40 with MaxDB 7.7.4 under windows installation, as following from RZ20:
Date Time Short name Object name User Name ALUSER16
Message
30.10.2009 12:55:26 Requests ContRep: ZCONTENT01 AXONBASIS HTTP_POST_DOCUME
HTTP error: 500 (Internal Server Error) " ;ODBC State 00000; Error Code 0"
30.10.2009 12:55:37 Requests ContRep: ZCONTENT01 AXONBASIS HTTP_POST_DOCUME
HTTP error: 500 (Internal Server Error) " ;ODBC State 00000; Error Code 0"
30.10.2009 12:55:49 Requests ContRep: ZCONTENT01 AXONBASIS HTTP_POST_DOCUME
HTTP error: 500 (Internal Server Error) " ;ODBC State 00000; Error Code 0"
30.10.2009 12:56:01 Requests ContRep: ZCONTENT01 AXONBASIS HTTP_POST_DOCUME
HTTP error: 500 (Internal Server Error) " ;ODBC State 00000; Error Code 0"
30.10.2009 13:31:22 Requests ContRep: ZCONTENT01 AXONBASIS HTTP_POST_FILES_
HTTP error: 500 (Internal Server Error) " ;ODBC State 00000; Error Code 0"
30.10.2009 13:31:45 Requests ContRep: ZCONTENT01 AXONBASIS HTTP_POST_FILES_
HTTP error: 500 (Internal Server Error) " ;ODBC State 00000; Error Code 0"
30.10.2009 13:51:05 Requests ContRep: ZCONTENT01 AXONBASIS HTTP_POST_FILES_
HTTP error: 500 (Internal Server Error) " ;ODBC State 00000; Error Code 0"
30.10.2009 13:51:31 Requests ContRep: ZCONTENT01 AXONBASIS HTTP_POST_FILES_
HTTP error: 500 (Internal Server Error) " ;ODBC State 00000; Error Code 0"
30.10.2009 14:03:08 Requests ContRep: ZCONTENT01 AXONBASIS HTTP_POST_FILES_
HTTP error: 500 (Internal Server Error) " ;ODBC State 00000; Error Code 0"
30.10.2009 14:03:38 Requests ContRep: ZCONTENT01 AXONBASIS HTTP_POST_FILES_
HTTP error: 500 (Internal Server Error) " ;ODBC State 00000; Error Code 0"
The error is happening while executing RSCMST report. Content Server installation and configuration finished successfully. I installed for 3 server, 2 of them don't have this kind of issue. Please need your expertise on this.
Thanks in advance.
Regards,
YanHi Natalia,
Thanks a lot for your suggestion. I've read the mentioned OSS last time while I was having the related issue. Now the issue had been solved by reinstall the content server. I though I did the wrong step while installing or upgrading the MaxDB.
With Best Regards,
Yan -
Install NetWeaver 7.31 with MaxDB 7.9
Dear Experts,
I'm trying to install NetWeaver 7.31 with MaxDB. According to MaxDB website, NetWeaver 7.31 requires MaxDB RDBMS 7.9. However, I couldn't find it in the SMP. Can anyone tell me where I can download the installation files? Thanks for your help.
IngridHi Ingrid,
Although this is a question to NW-related forum, MaxDB 7.9 package is located on the same page where you can download SAP EHP1 FOR SAP NETWEAVER 7.3:
go to Software Download Center > Installation and Upgrades > A-Z Index > N > SAP NETWEAVER > SAP EHP1 FOR SAP NETWEAVER 7.3 > "Installation and Upgrade" link > Microsoft Windows > MaxBD (SAPDB) > underneath you will see 51044253_5, 51044253_6 and 51044253_7 packages. Chose the one that you need.
Regards,
Sergiy -
Hello
Is it possible to install SAP MOBILE PLATFORM with MAXDB?
In the installation document I saw that there was 3 choices (ASE, DB2, ORACLE).
Someone tried to install it with MAXDB?
Thank you and good day.
Tags edited by: jitendra kansalAs per official document it doesn't mention anything about MaxDB. Using a Custom Database
Also, If you have access to SAP support portal, you can check Note 1934552 , It has defined some persistence databases supported by SMP 3.0 server.
Database Type
Platforms Supported
Version
Derby Database
Windows
Linux
10.8.x / 10.9.x
Oracle Database
Windows
Linux
Solaris
IBM AIX
11G
Sybase Adaptive Server
Enterprise
Windows,
Linux
Solaris
15.5 or Later
IBM DB2
Windows,
Linux
Solaris
IBM AIX
UDB 10.1
(source: SAP Note 1934552)
Note: Again, Derby DB is only for Developer and POC installations not for Production.
Rgrds,
Jitendra -
Database selection with invalid cursor with MaxDB database
Hi Experts,
I encountered the this error:
"Database selection with invalid cursor
The database interface was called by a cursor (in a FETCH or CLOSE
cursor operation) that is not flagged as opened. This can occur if a
COMMIT or ROLLBACK was executed within a SELECT loop (which closes all
opened cursors), followed by another attempt to access the cursor (for
example, the next time the loop is executed)."
We are using bw support package 19 early this month. Previously is working fine but this problem occured from the last 2 days.
We are using MaxDB database.
Really appreciate any speedy responds.Hi,
We finally resolved the issue.
The solution:
We check the RFC connection test in SM59. There are connection error.
There is an error that related J2EE_ADMIN user.
SO we reset the J2EE_ADMIN id in SU01.
The problem goes away.
Many thanks -
Poor restore performance with MaxDB 7.6.04.15 and HP Data Protector 6
We encounter severe problems with the MaxDB integration in Data Protector 6. While the backup is finished in two hours (LTO4), the restore takes 9-12 hours.
The source system has the following specs:
CPU: 4x QuadCore
RAM: 48 GB
Cache Size: 25 GB
db size (allocated): 550 GB
27x 30 GB raw devices, located in SAN
SLES 10 SP2
parallelism (# pipes): 14 (tried 4, 8, 28, 2 tapes...)
Target system:
CPU: 2x DualCore
RAM: 8 GB
Cache Size: 4 GB
27x 30 GB raw devices, located in SAN
SLES 10 SP2
We checked the performance of file system restores - works fine with good restore times, so we don't think it's a SAN/tape library issue (e. g. switches etc.).
Some things are quite disturbing:
x_cons <SID> show sus
SERVERDB: <SID>
List of suspend-reasons:
========================
Total Suspends: 428083
Vsuspend (203) : 426288 ( 99.58% ) kb39read_wait
Vsuspend (204) : 1611 ( 0.38% ) kb39write_wait
JobWait BckRec : 1 ( 0.00% ) SrvTasks_BackupServer::WaitForAnyJobFini
No-Work (255) : 183 ( 0.04% ) Task is waiting for work
x_cons <SID> show tasks|grep BUP
T71 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
T72 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
T73 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
T74 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
T75 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
T76 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T77 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T78 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T79 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T80 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T81 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T82 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T83 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T84 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T85 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T86 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T87 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T88 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T89 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
T92 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
T109 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
T111 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T112 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T128 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T129 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T130 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T131 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T132 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T133 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T134 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T135 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T136 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T137 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T138 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T139 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T140 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T141 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T142 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T143 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T144 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
T148 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
I tried changing parameters a bit with no visible effort. The current parameters of the target system are:
2008-09-16 15:54:01 6300 20235 RTE ADMIN=1
2008-09-16 15:54:01 6300 20235 RTE _AK_DUMP_ALLOWED=YES
2008-09-16 15:54:01 6300 20235 RTE ALLOW_MULTIPLE_SERVERTASK_UKTS=YES
2008-09-16 15:54:01 6300 20235 RTE AUTHENTICATION_ALLOW=
2008-09-16 15:54:01 6300 20235 RTE AUTHENTICATION_DENY=
2008-09-16 15:54:01 6300 20235 RTE AUTOSAVE=1
2008-09-16 15:54:01 6300 20235 RTE AUTO_RECREATE_BAD_INDEXES=YES
2008-09-16 15:54:01 6300 20235 RTE BACKUPRESULT=1
2008-09-16 15:54:01 6300 20235 RTE BACKUP_BLOCK_CNT=64
2008-09-16 15:54:01 6300 20235 RTE _BACKUP_HISTFILE=dbm.knl
2008-09-16 15:54:01 6300 20235 RTE _BACKUP_MED_DEF=dbm.mdf
2008-09-16 15:54:01 6300 20235 RTE CACHE_IN_SHARED_MEMORY=NO
2008-09-16 15:54:01 6300 20235 RTE CACHE_SIZE=512000
2008-09-16 15:54:01 6300 20235 RTE CALLSTACKLEVEL=0
2008-09-16 15:54:01 6300 20235 RTE _CAT_CACHE_MINSIZE=262144
2008-09-16 15:54:01 6300 20235 RTE CAT_CACHE_SUPPLY=12864
2008-09-16 15:54:01 6300 20235 RTE CHECKDATA=1
2008-09-16 15:54:01 6300 20235 RTE CHECK_BACKUP=NO
2008-09-16 15:54:01 6300 20235 RTE CHECK_COMMON=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_CONVERTER=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_DATACACHE=NO
2008-09-16 15:54:01 6300 20235 RTE CHECK_DATAINDEX=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_DATAPAGELOG=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_FBM=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_HASHED_RESULTSET=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_IOMAN=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_KB_REGIONS=NO
2008-09-16 15:54:01 6300 20235 RTE CHECK_LOCK_SUPPLY=NO
2008-09-16 15:54:01 6300 20235 RTE CHECK_LOCK=NO
2008-09-16 15:54:01 6300 20235 RTE CHECK_LOGHISTORY=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_LOGPAGE=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_LOGTRANS=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_LOGVOLUME=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_QUERYREWRITE=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_REGIONS=NO
2008-09-16 15:54:01 6300 20235 RTE CHECK_SRVTASKS=0
2008-09-16 15:54:01 6300 20235 RTE CHECK_TABLE_WIDTH=NO
2008-09-16 15:54:01 6300 20235 RTE CHECK_TASK_SPECIFIC_CATALOGCACHE=NO
2008-09-16 15:54:01 6300 20235 RTE CHECK_TRANSLIST=NO
2008-09-16 15:54:01 6300 20235 RTE CHECK_TREE_LOCKS=NO
2008-09-16 15:54:01 6300 20235 RTE CHECK_TREE=NO
2008-09-16 15:54:01 6300 20235 RTE CLUSTERED_LOBS=NO
2008-09-16 15:54:01 6300 20235 RTE CLUSTER_WRITE_THRESHOLD=80
2008-09-16 15:54:01 6300 20235 RTE COLUMNCOMPRESSION=YES
2008-09-16 15:54:01 6300 20235 RTE _COMMENT=
2008-09-16 15:54:01 6300 20235 RTE CONTROLPASSWORD=***
2008-09-16 15:54:01 6300 20235 RTE CONTROLUSERID=CONTROL
2008-09-16 15:54:01 6300 20235 RTE CONVERTER_REGIONS=64
2008-09-16 15:54:01 6300 20235 RTE DATABASEFULL=1
2008-09-16 15:54:01 6300 20235 RTE _DATA_CACHE_RGNS=64
2008-09-16 15:54:01 6300 20235 RTE DATA_IO_BLOCK_COUNT=64
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_GROUPS=1
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0001=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0002=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0003=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0004=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0005=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0006=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0007=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0008=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0009=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0010=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0011=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0012=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0013=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0014=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0015=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0016=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0017=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0018=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0019=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0020=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0021=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0022=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0023=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0024=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0025=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0026=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_MODE_0027=NORMAL
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0001=/dev/raw/raw1
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0002=/dev/raw/raw2
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0003=/dev/raw/raw3
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0004=/dev/raw/raw4
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0005=/dev/raw/raw5
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0006=/dev/raw/raw6
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0007=/dev/raw/raw7
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0008=/dev/raw/raw8
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0009=/dev/raw/raw9
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0010=/dev/raw/raw10
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0011=/dev/raw/raw11
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0012=/dev/raw/raw12
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0013=/dev/raw/raw13
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0014=/dev/raw/raw14
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0015=/dev/raw/raw15
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0016=/dev/raw/raw16
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0017=/dev/raw/raw17
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0018=/dev/raw/raw18
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0019=/dev/raw/raw19
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0020=/dev/raw/raw20
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0021=/dev/raw/raw21
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0022=/dev/raw/raw22
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0023=/dev/raw/raw23
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0024=/dev/raw/raw24
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0025=/dev/raw/raw25
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0026=/dev/raw/raw26
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_NAME_0027=/dev/raw/raw27
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0001=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0002=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0003=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0004=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0005=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0006=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0007=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0008=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0009=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0010=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0011=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0012=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0013=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0014=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0015=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0016=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0017=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0018=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0019=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0020=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0021=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0022=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0023=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0024=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0025=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0026=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_SIZE_0027=3932160
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0001=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0002=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0003=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0004=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0005=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0006=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0007=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0008=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0009=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0010=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0011=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0012=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0013=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0014=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0015=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0016=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0017=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0018=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0019=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0020=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0021=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0022=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0023=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0024=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0025=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0026=R
2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0027=R
2008-09-16 15:54:01 6300 20235 RTE DATE_TIME_FORMAT=INTERNAL
2008-09-16 15:54:01 6300 20235 RTE DBFILLINGABOVELIMIT=70L80M85M90H95H96H97H98H99H
2008-09-16 15:54:01 6300 20235 RTE DBFILLINGBELOWLIMIT=70L80L85L90L95L
2008-09-16 15:54:01 6300 20235 RTE DDLTRIGGER=YES
2008-09-16 15:54:01 6300 20235 RTE DEADLOCK_DETECTION=4
2008-09-16 15:54:01 6300 20235 RTE DEFAULT_CODE=ASCII
2008-09-16 15:54:01 6300 20235 RTE _DELAY_COMMIT=NO
2008-09-16 15:54:01 6300 20235 RTE _DELAY_LOGWRITER=0
2008-09-16 15:54:01 6300 20235 RTE DIAG_HISTORY_NUM=2
2008-09-16 15:54:01 6300 20235 RTE DIAG_HISTORY_PATH=/sapdb/data/wrk/PSR/DIAGHISTORY
2008-09-16 15:54:01 6300 20235 RTE _DIAG_SEM=0
2008-09-16 15:54:01 6300 20235 RTE _DW_IO_AREA_FLUSH=50
2008-09-16 15:54:01 6300 20235 RTE _DW_IO_AREA_SIZE=50
2008-09-16 15:54:01 6300 20235 RTE _DW_LRU_TAIL_FLUSH=25
2008-09-16 15:54:01 6300 20235 RTE _DYN_TASK_STACK=NO
2008-09-16 15:54:01 6300 20235 RTE ENABLE_CHECK_INSTANCE=YES
2008-09-16 15:54:01 6300 20235 RTE ENABLE_SYSTEM_TRIGGERS=YES
2008-09-16 15:54:01 6300 20235 RTE ERROR=3
2008-09-16 15:54:01 6300 20235 RTE _EVENTFILE=knldiag.evt
2008-09-16 15:54:01 6300 20235 RTE _EVENTSIZE=0
2008-09-16 15:54:01 6300 20235 RTE EVENT=1
2008-09-16 15:54:01 6300 20235 RTE EXPAND_COM_TRACE=NO
2008-09-16 15:54:01 6300 20235 RTE EXTERNAL_DUMP_REQUEST=NO
2008-09-16 15:54:01 6300 20235 RTE FBM_CLUSTER_MODE=MIXED
2008-09-16 15:54:01 6300 20235 RTE _FBM_LOW_IO_RATE=10
2008-09-16 15:54:01 6300 20235 RTE FBM_VOLUME_BALANCE=10
2008-09-16 15:54:01 6300 20235 RTE FBM_VOLUME_COMPRESSION=50
2008-09-16 15:54:01 6300 20235 RTE FILEDIR_SPINLOCKPOOL_SIZE=10
2008-09-16 15:54:01 6300 20235 RTE FORBID_LOAD_BALANCING=YES
2008-09-16 15:54:01 6300 20235 RTE FORMATTING_MODE=PARALLEL
2008-09-16 15:54:01 6300 20235 RTE FORMAT_DATAVOLUME=YES
2008-09-16 15:54:01 6300 20235 RTE HASHED_RESULTSET_CACHESIZE=262144
2008-09-16 15:54:01 6300 20235 RTE HASHED_RESULTSET=YES
2008-09-16 15:54:01 6300 20235 RTE HEAP_CHECK_LEVEL=0
2008-09-16 15:54:01 6300 20235 RTE HIRES_TIMER_TYPE=CPU
2008-09-16 15:54:01 6300 20235 RTE HS_STORAGE_DLL=libhsscopy
2008-09-16 15:54:01 6300 20235 RTE HS_SYNC_INTERVAL=50
2008-09-16 15:54:01 6300 20235 RTE _IDXFILE_LIST_SIZE=2048
2008-09-16 15:54:01 6300 20235 RTE INDEX_LEAF_CACHING=2
2008-09-16 15:54:01 6300 20235 RTE INIT_ALLOCATORSIZE=262144
2008-09-16 15:54:01 6300 20235 RTE INSTANCE_TYPE=OLTP
2008-09-16 15:54:01 6300 20235 RTE _IOPROCS_FOR_PRIO=0
2008-09-16 15:54:01 6300 20235 RTE _IOPROCS_FOR_READER=1
2008-09-16 15:54:01 6300 20235 RTE _IOPROCS_PER_DEV=2
2008-09-16 15:54:01 6300 20235 RTE _IOPROCS_SWITCH=2
2008-09-16 15:54:01 6300 20235 RTE JOIN_MAXTAB_LEVEL4=64
2008-09-16 15:54:01 6300 20235 RTE JOIN_MAXTAB_LEVEL9=5
2008-09-16 15:54:01 6300 20235 RTE JOIN_SEARCH_LEVEL=0
2008-09-16 15:54:01 6300 20235 RTE JOIN_TABLEBUFFER=128
2008-09-16 15:54:01 6300 20235 RTE _KERNELDIAGFILE=knldiag
2008-09-16 15:54:01 6300 20235 RTE KERNELDIAGSIZE=800
2008-09-16 15:54:01 6300 20235 RTE _KERNELDUMPFILE=knldump
2008-09-16 15:54:01 6300 20235 RTE _KERNELTRACEFILE=knltrace
2008-09-16 15:54:01 6300 20235 RTE KERNELTRACESIZE=2809
2008-09-16 15:54:01 6300 20235 RTE KERNELVERSION=KERNEL 7.6.04 BUILD 015-123-189-221
2008-09-16 15:54:01 6300 20235 RTE _LM_LOCK_REGIONS=0
2008-09-16 15:54:01 6300 20235 RTE _LM_REQUEST_REGIONS=0
2008-09-16 15:54:01 6300 20235 RTE _LM_TRANS_REGIONS=0
2008-09-16 15:54:01 6300 20235 RTE LOAD_BALANCING_CHK=0
2008-09-16 15:54:01 6300 20235 RTE LOAD_BALANCING_DIF=10
2008-09-16 15:54:01 6300 20235 RTE LOAD_BALANCING_EQ=5
2008-09-16 15:54:01 6300 20235 RTE LOCAL_REDO_LOG_BUFFER_SIZE=0
2008-09-16 15:54:01 6300 20235 RTE _LOCKMANAGER_ENABLED=NO
2008-09-16 15:54:01 6300 20235 RTE _LOCK_SUPPLY_BLOCK=100
2008-09-16 15:54:01 6300 20235 RTE LOGABOVELIMIT=50L75L90M95M96H97H98H99H
2008-09-16 15:54:01 6300 20235 RTE LOGFULL=1
2008-09-16 15:54:01 6300 20235 RTE LOGSEGMENTFULL=1
2008-09-16 15:54:01 6300 20235 RTE LOG_BACKUP_TO_PIPE=NO
2008-09-16 15:54:01 6300 20235 RTE LOG_IO_BLOCK_COUNT=8
2008-09-16 15:54:01 6300 20235 RTE LOG_IO_QUEUE=200
2008-09-16 15:54:01 6300 20235 RTE LOG_MIRRORED=NO
2008-09-16 15:54:01 6300 20235 RTE LOG_QUEUE_COUNT=1
2008-09-16 15:54:01 6300 20235 RTE LOG_SEGMENT_SIZE=129024
2008-09-16 15:54:01 6300 20235 RTE LOG_VOLUME_NAME_001=/dev/raw/raw28
2008-09-16 15:54:01 6300 20235 RTE LOG_VOLUME_NAME_002=/dev/raw/raw29
2008-09-16 15:54:01 6300 20235 RTE LOG_VOLUME_SIZE_001=524288
2008-09-16 15:54:01 6300 20235 RTE LOG_VOLUME_SIZE_002=524288
2008-09-16 15:54:01 6300 20235 RTE LOG_VOLUME_TYPE_001=R
2008-09-16 15:54:01 6300 20235 RTE LOG_VOLUME_TYPE_002=R
2008-09-16 15:54:01 6300 20235 RTE LRU_FOR_SCAN=NO
2008-09-16 15:54:01 6300 20235 RTE MAXBACKUPDEVS=32
2008-09-16 15:54:01 6300 20235 RTE MAXCPU=3
2008-09-16 15:54:01 6300 20235 RTE MAXDATAVOLUMES=40
2008-09-16 15:54:01 6300 20235 RTE _MAXEVENTS=100
2008-09-16 15:54:01 6300 20235 RTE _MAXEVENTTASKS=2
2008-09-16 15:54:01 6300 20235 RTE _MAXGARBAGE_COLL=1
2008-09-16 15:54:01 6300 20235 RTE MAXLOCKS=1000000
2008-09-16 15:54:01 6300 20235 RTE MAXLOGVOLUMES=4
2008-09-16 15:54:01 6300 20235 RTE MAXPAGER=64
2008-09-16 15:54:01 6300 20235 RTE MAXRGN_REQUEST=-1
2008-09-16 15:54:01 6300 20235 RTE MAXSERVERTASKS=116
2008-09-16 15:54:01 6300 20235 RTE _MAXTASK_STACK=512
2008-09-16 15:54:01 6300 20235 RTE _MAXTRANS=1604
2008-09-16 15:54:01 6300 20235 RTE MAXUSERTASKS=200
2008-09-16 15:54:01 6300 20235 RTE MAXVOLUMES=45
2008-09-16 15:54:01 6300 20235 RTE MAX_HASHTABLE_MEMORY=5120
2008-09-16 15:54:01 6300 20235 RTE MAX_LOG_QUEUE_COUNT=0
2008-09-16 15:54:01 6300 20235 RTE _MAX_MESSAGE_FILES=0
2008-09-16 15:54:01 6300 20235 RTE MAX_MESSAGE_LIST_LENGTH=100
2008-09-16 15:54:01 6300 20235 RTE MAX_RETENTION_TIME=480
2008-09-16 15:54:01 6300 20235 RTE MAX_SERVERTASK_STACK=500
2008-09-16 15:54:01 6300 20235 RTE MAX_SINGLE_HASHTABLE_SIZE=512
2008-09-16 15:54:01 6300 20235 RTE MAX_SPECIALTASK_STACK=500
2008-09-16 15:54:01 6300 20235 RTE _MBLOCK_DATA_SIZE=32768
2008-09-16 15:54:01 6300 20235 RTE _MBLOCK_QUAL_SIZE=32768
2008-09-16 15:54:01 6300 20235 RTE _MBLOCK_STACK_SIZE=32768
2008-09-16 15:54:01 6300 20235 RTE _MBLOCK_STRAT_SIZE=16384
2008-09-16 15:54:01 6300 20235 RTE MCOD=NO
2008-09-16 15:54:01 6300 20235 RTE MEMORY_ALLOCATION_LIMIT=0
2008-09-16 15:54:01 6300 20235 RTE _MINREPLY_SIZE=4096
2008-09-16 15:54:01 6300 20235 RTE MINSERVERTASKS=116
2008-09-16 15:54:01 6300 20235 RTE MIN_RETENTION_TIME=60
2008-09-16 15:54:01 6300 20235 RTE MONITOR_READ=2147483647
2008-09-16 15:54:01 6300 20235 RTE MONITOR_ROWNO=0
2008-09-16 15:54:01 6300 20235 RTE MONITOR_SELECTIVITY=0
2008-09-16 15:54:01 6300 20235 RTE MONITOR_TIME=2147483647
2008-09-16 15:54:01 6300 20235 RTE _MP_DISP_LOOPS=2
2008-09-16 15:54:01 6300 20235 RTE _MP_DISP_PRIO=DEFAULT
2008-09-16 15:54:01 6300 20235 RTE _MP_RGN_BUSY_WAIT=DEFAULT
2008-09-16 15:54:01 6300 20235 RTE _MP_RGN_DIRTY_READ=DEFAULT
2008-09-16 15:54:01 6300 20235 RTE MP_RGN_LOOP=-1
2008-09-16 15:54:01 6300 20235 RTE _MP_RGN_PRIO=DEFAULT
2008-09-16 15:54:01 6300 20235 RTE _MP_RGN_QUEUE=YES
2008-09-16 15:54:01 6300 20235 RTE NO_SYNC_TO_DISK_WANTED=NO
2008-09-16 15:54:01 6300 20235 RTE OFFICIAL_NODE=
2008-09-16 15:54:01 6300 20235 RTE OMS_HEAP_BLOCKSIZE=10000
2008-09-16 15:54:01 6300 20235 RTE OMS_HEAP_COUNT=8
2008-09-16 15:54:01 6300 20235 RTE OMS_HEAP_LIMIT=0
2008-09-16 15:54:01 6300 20235 RTE OMS_HEAP_THRESHOLD=100
2008-09-16 15:54:01 6300 20235 RTE _OMS_REGIONS=0
2008-09-16 15:54:01 6300 20235 RTE _OMS_RGNS=7
2008-09-16 15:54:01 6300 20235 RTE OMS_RUN_IN_UDE_SERVER=NO
2008-09-16 15:54:01 6300 20235 RTE OMS_STREAM_TIMEOUT=30
2008-09-16 15:54:01 6300 20235 RTE OMS_VERS_THRESHOLD=2097152
2008-09-16 15:54:01 6300 20235 RTE ONLINE=1
2008-09-16 15:54:01 6300 20235 RTE OPMSG1=/dev/console
2008-09-16 15:54:01 6300 20235 RTE OPMSG2=/dev/null
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_AGGREGATION=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_FETCH_REVERSE=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_FIRST_ROWS=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_JOIN_HASHTABLE=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_JOIN_HASH_MINIMAL_RATIO=1
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_JOIN_ONEPHASE=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_JOIN_OPERATOR_SORT=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_JOIN_OUTER=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_JOIN_PARALLEL_MINSIZE=1000000
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_JOIN_PARALLEL_SERVERS=0
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_MIN_MAX=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_OPERATOR_JOIN_COSTFUNC=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_OPERATOR_JOIN=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_QUAL_ON_INDEX=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_QUERYREWRITE=OPERATOR
2008-09-16 15:54:01 6300 20235 RTE OPTIMIZE_STAR_JOIN=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIM_CACHE=NO
2008-09-16 15:54:01 6300 20235 RTE OPTIM_INV_ONLY=YES
2008-09-16 15:54:01 6300 20235 RTE OPTIM_JOIN_FETCH=0
2008-09-16 15:54:01 6300 20235 RTE OPTIM_MAX_MERGE=500
2008-09-16 15:54:01 6300 20235 RTE OUTOFSESSIONS=3
2008-09-16 15:54:01 6300 20235 RTE _PACKET_SIZE=131072
2008-09-16 15:54:01 6300 20235 RTE _PAGE_SIZE=8192
2008-09-16 15:54:01 6300 20235 RTE PREALLOCATE_IOWORKER=NO
2008-09-16 15:54:01 6300 20235 RTE _PRIO_BASE_COM=10
2008-09-16 15:54:01 6300 20235 RTE _PRIO_BASE_IOC=80
2008-09-16 15:54:01 6300 20235 RTE _PRIO_BASE_RAV=80
2008-09-16 15:54:01 6300 20235 RTE _PRIO_BASE_REX=40
2008-09-16 15:54:01 6300 20235 RTE _PRIO_BASE_U2U=100
2008-09-16 15:54:01 6300 20235 RTE _PRIO_FACTOR=80
2008-09-16 15:54:01 6300 20235 RTE PROTECT_DATACACHE_MEMORY=NO
2008-09-16 15:54:01 6300 20235 RTE _READAHEAD_BLOBS=32
2008-09-16 15:54:01 6300 20235 RTE REQUEST_TIMEOUT=5000
2008-09-16 15:54:01 6300 20235 RTE RESERVEDSERVERTASKS=75
2008-09-16 15:54:01 6300 20235 RTE _RESTART_TIME=600
2008-09-16 15:54:01 6300 20235 RTE ROW_LOCKS_PER_TRANSACTION=50
2008-09-16 15:54:01 6300 20235 RTE _ROW_RGNS=8
2008-09-16 15:54:01 6300 20235 RTE _RTEDUMPFILE=rtedump
2008-09-16 15:54:01 6300 20235 RTE RTE_TEST_REGIONS=0
2008-09-16 15:54:01 6300 20235 RTE RUNDIRECTORY=/sapdb/data/wrk/PSR
2008-09-16 15:54:01 6300 20235 RTE SEQUENCE_CACHE=1
2008-09-16 15:54:01 6300 20235 RTE _SERVERDB_FOR_SAP=YES
2008-09-16 15:54:01 6300 20235 RTE SESSION_TIMEOUT=900
2008-09-16 15:54:01 6300 20235 RTE SET_VOLUME_LOCK=YES
2008-09-16 15:54:01 6300 20235 RTE SHAREDSQL_CLEANUPTHRESHOLD=25
2008-09-16 15:54:01 6300 20235 RTE SHAREDSQL_COMMANDCACHESIZE=262144
2008-09-16 15:54:01 6300 20235 RTE SHAREDSQL=YES
2008-09-16 15:54:01 6300 20235 RTE _SHMKERNEL=24377
2008-09-16 15:54:01 6300 20235 RTE SHOW_MAX_KB_STACK_USE=NO
2008-09-16 15:54:01 6300 20235 RTE SHOW_MAX_STACK_USE=NO
2008-09-16 15:54:01 6300 20235 RTE SIMULATE_VECTORIO=NEVER
2008-09-16 15:54:01 6300 20235 RTE SPINLOCK_BACKOFF_BASE=1
2008-09-16 15:54:01 6300 20235 RTE SPINLOCK_BACKOFF_FACTOR=2
2008-09-16 15:54:01 6300 20235 RTE SPINLOCK_BACKOFF_MAXIMUM=64
2008-09-16 15:54:01 6300 20235 RTE SPINLOCK_LOOP_COUNT=30000
2008-09-16 15:54:01 6300 20235 RTE STANDBY=1
2008-09-16 15:54:01 6300 20235 RTE SUBTREE_LOCKS=NO
2008-09-16 15:54:01 6300 20235 RTE SUPPRESS_CORE=YES
2008-09-16 15:54:01 6300 20235 RTE SYMBOL_DEMANGLING=NO
2008-09-16 15:54:01 6300 20235 RTE SYMBOL_RESOLUTION=YES
2008-09-16 15:54:01 6300 20235 RTE SYSTEMERROR=3
2008-09-16 15:54:01 6300 20235 RTE _TAB_RGNS=8
2008-09-16 15:54:01 6300 20235 RTE _TASKCLUSTER_01=tw;al;ut;100*bup;10*ev,10*gc;
2008-09-16 15:54:01 6300 20235 RTE _TASKCLUSTER_02=ti,100*dw;67*us,39*sv;
2008-09-16 15:54:01 6300 20235 RTE _TASKCLUSTER_03=equalize
2008-09-16 15:54:01 6300 20235 RTE TIME_MEASUREMENT=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_AK=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_ALLOCATOR=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_CATALOG=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_CLIENTKERNELCOM=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_COMMON=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_COMMUNICATION=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_CONVERTER=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_DATACACHE=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_DATACHAIN=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_DATAINDEX=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_DATAPAM=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_DATATREE=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_DBPROC=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_DEFAULT=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_DELETE=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_FBM=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_FILEDIR=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_FRAMECTRL=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_INDEX=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_INSERT=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_IOMAN=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_IPC=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_JOIN=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_KSQL=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_LOCKMANAGER=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_LOCK=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_LOGACTION=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_LOGHISTORY=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_LOGPAGE=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_LOGTRANS=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_LOGVOLUME=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_LONG=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_MEMORY=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_MESSAGES=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OBJECTCONTAINER=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OBJECT_ADD=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_OBJECT_ALTER=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_OBJECT_FREE=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_OBJECT_GET=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_OBJECT=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_CONTAINERDIR=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_CONTEXT=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_ERROR=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_FLUSHCACHE=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_INTERFACE=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_KEYRANGE=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_KEY=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_LOCK=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_MEMORY=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_NEWOBJ=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_SESSION=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_STREAM=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_VAROBJECT=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OMS_VERSION=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_OPTIMIZE=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_ORDER_STANDARD=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_ORDER=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_PAGER=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_PAGES_BUP=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_PAGES_EV=2
2008-09-16 15:54:01 6300 20235 RTE TRACE_PAGES_GC=20
2008-09-16 15:54:01 6300 20235 RTE TRACE_PAGES_LW=5
2008-09-16 15:54:01 6300 20235 RTE TRACE_PAGES_PG=3
2008-09-16 15:54:01 6300 20235 RTE TRACE_PAGES_SV=5
2008-09-16 15:54:01 6300 20235 RTE TRACE_PAGES_TI=2
2008-09-16 15:54:01 6300 20235 RTE TRACE_PAGES_US=10
2008-09-16 15:54:01 6300 20235 RTE TRACE_PAGES_UT=5
2008-09-16 15:54:01 6300 20235 RTE TRACE_PAGES=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_PRIMARY_TREE=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_QUERYREWRITE=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_RUNTIME=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_SELECT=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_SHAREDSQL=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_SQLMANAGER=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_SRVTASKS=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_STOP_ERRORCODE=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_SYNCHRONISATION=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_SYSVIEW=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_TABLE=0
2008-09-16 15:54:01 6300 20235 RTE TRACE_TIME=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_UPDATE=NO
2008-09-16 15:54:01 6300 20235 RTE TRACE_VOLUME=0
2008-09-16 15:54:01 6300 20235 RTE TRANS_HISTORY_SIZE=0
2008-09-16 15:54:01 6300 20235 RTE _TRANS_RGNS=8
2008-09-16 15:54:01 6300 20235 RTE TRANS_THRESHOLD_VALUE=60
2008-09-16 15:54:01 6300 20235 RTE UKT_CPU_RELATIONSHIP=NONE
2008-09-16 15:54:01 6300 20235 RTE _UNICODE=YES
2008-09-16 15:54:01 6300 20235 RTE UPDATESTAT_PARALLEL_SERVERS=0
2008-09-16 15:54:01 6300 20235 RTE UPDATESTAT_SAMPLE_ALGO=1
2008-09-16 15:54:01 6300 20235 RTE UPDSTATWANTED=1
2008-09-16 15:54:01 6300 20235 RTE USED_MAX_LOG_QUEUE_COUNT=3
2008-09-16 15:54:01 6300 20235 RTE USESELECTFETCH=YES
2008-09-16 15:54:01 6300 20235 RTE USEUNICODECOLUMNCOMPRESSION=NO
2008-09-16 15:54:01 6300 20235 RTE USEVARIABLEINPUT=NO
2008-09-16 15:54:01 6300 20235 RTE USE_COROUTINES=YES
2008-09-16 15:54:01 6300 20235 RTE _USE_IOPROCS_ONLY=NO
2008-09-16 15:54:01 6300 20235 RTE USE_OPEN_DIRECT_FOR_BACKUP=YES
2008-09-16 15:54:01 6300 20235 RTE USE_OPEN_DIRECT=YES
2008-09-16 15:54:01 6300 20235 RTE USE_SYSTEM_PAGE_CACHE=YES
2008-09-16 15:54:01 6300 20235 RTE _UTILITY_PROTFILE=dbm.utl
2008-09-16 15:54:01 6300 20235 RTE UTILITY_PROTSIZE=100
2008-09-16 15:54:01 6300 20235 RTE VOLUMENO_BIT_COUNT=8
2008-09-16 15:54:01 6300 20235 RTE _WORKDATA_SIZE=8192
2008-09-16 15:54:01 6300 20235 RTE _WORKSTACK_SIZE=8192
2008-09-16 15:54:01 6300 20235 RTE XP_CONVERTER_REGIONS=0
2008-09-16 15:54:01 6300 20235 RTE XP_DATA_CACHE_RGNS=0
2008-09-16 15:54:01 6300 20235 RTE XP_MAXPAGER=0> Some things are quite disturbing:
>
>
x_cons <SID> show sus
>
> SERVERDB: <SID>
>
> List of suspend-reasons:
> ========================
>
> Total Suspends: 428083
>
> Vsuspend (203) : 426288 ( 99.58% ) kb39read_wait
> Vsuspend (204) : 1611 ( 0.38% ) kb39write_wait
> JobWait BckRec : 1 ( 0.00% ) SrvTasks_BackupServer::WaitForAnyJobFini
> No-Work (255) : 183 ( 0.04% ) Task is waiting for work
What exactly do you find disturbing with that information?
All we see here is how often a specific suspend had been triggered since the database was started. We don't see how long these suspends took and neither do we know what the suspend reason is, that would be important for your current issue.
>
x_cons <SID> show tasks|grep BUP
> T71 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
> T72 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
> T73 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
> T74 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
> T75 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
> T76 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T77 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T78 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T79 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T80 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T81 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T82 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T83 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T84 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T85 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T86 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T87 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T88 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T89 6 -1 BUPmed -1 Vsuspend (203) 0 0 1027577(s)
> T92 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
> T109 6 -1 BUPvol -1 AsynWaitWrite 0 0 1027577(s)
> T111 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T112 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T128 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T129 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T130 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T131 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T132 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T133 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T134 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T135 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T136 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T137 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T138 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T139 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T140 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T141 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T142 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T143 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T144 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
> T148 7 -1 BUPvol -1 AsynWaitWrite 0 0 345248(s)
Ok, here we see that the MaxDB kernel is waiting for writes to the datavolumes to get finished. As we've only one snapshot here, we cannot tell anything more from it. You either should perform several snapshots in a row, or (better!) use the DBAnalyzer with a short sample interval, say 60 seconds.
Also you should enable the time measurement, so that we can have some I/O related timing information.
> I tried changing parameters a bit with no visible effort. The current parameters of the target system are:
What parameters did you change? Why? And to what values did you set them?
>
> 2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0001=R
> 2008-09-16 15:54:01 6300 20235 RTE DATA_VOLUME_TYPE_0002=R
Ok, since you use RAW devices (good choice!) there shouldn't be any issues with the I/O on the OS level.
What's left is: how are the RAW devices physically stored?
Could it be that writing to your RAW devices is pretty expensive?
Ah - before I forget: if you're a SAP customer this should be investigated in a support message!
Best regards,
Lars -
Error in Netweaver installation with MaxDB on a 64-bit IA windows 2003
Hello all,
I am installing Netweaver CE 7.1 in Windows 2003. Out of the 35 phases , i am getting an error in the 13th phase. The name of the Phase is " Create Database Instance" . An error log is created and the details are as below :
Subprocess starts at 20091014155346
Execute Command : C:\Program Files\sdb\programs\pgm\dbmcli.exe -n SGPSRV011 -d SMD -u CONTROL,******** db_start
Execute Session Command : exit
Subprocess stops at 20091014155349
Subprocess call failedERR
-24994,ERR_RTE: Runtime environment error
1,'SMD' has stopped unexpectedly, (view 'Application Event Log') (OS error code 11000)
This is the text of the error being displayed :
An error occurred while processing service SAP NetWeaver CE Productive Edition > Installation Options > Standard System > Standard System. You may now
choose Retry to repeat the current step.
choose View Log to get more information about the error.
stop the task and continue with it later.
Log files are written to C:\Program Files/sapinst_instdir/CE71_PROD_ADA/INSTALL/ADA/STD/AS.
I feel that this error has something to do with the settings in the MaxDB database. Can you please help which setting needs to be changed ? Both the Netweaver and the MaxDB are on the same 64-bit Itanium server and the OS is Windows 2003.
Thanks and Regards
VijayCheck your max db database build, [https://service.sap.com/pam] and apply a patch if available. Also, you may want to log a problem on SMP.
-
Hello everyone. I have a problem with starting the system on MaxDB (Windows Server 2003).
First was an error :
No volume on compressed file 'c:\sapdb\S00\sapdata\DISKD0001', i change the properties (uncompress file), but now i get a new error message:
-24988 SQL error [db_online -f]; -9407, System error: unexpected error
This is KNLDIAG.ERR:
2010-05-11 15:59:43 0x14B0 19633 CONNECT Connect req. (T69, Node:'', PID:5288)
2010-05-11 15:59:43 0x14B0 19615 VOLUMEIO Attaching volume 'C:\sapdb\S00\sapdata\DISKD0001'
2010-05-11 15:59:43 0x151C 19613 DBSTATE I/O thread for 'C:\sapdb\S00\sapdata\DISKD0001' started
2010-05-11 15:59:43 0x14B0 19617 VOLUMEIO Single I/O attach, 'C:\sapdb\S00\sapdata\DISKD0001', UKT:7
2010-05-11 15:59:43 0x14B0 19615 VOLUMEIO Attaching volume 'C:\sapdb\S00\saplog\DISKL001'
2010-05-11 15:59:43 0x540 19613 DBSTATE I/O thread for 'C:\sapdb\S00\saplog\DISKL001' started
2010-05-11 15:59:44 0x14B0 19617 VOLUMEIO Single I/O attach, 'C:\sapdb\S00\saplog\DISKL001', UKT:7
2010-05-11 15:59:44 0x14B0 20016 Pager Start Read Converter
2010-05-11 15:59:44 0x14B0 20017 Pager Stop Read Converter, Pages: 5 IO: 5
2010-05-11 15:59:44 0x14B0 53000 DATACACH Begin data cache restart
2010-05-11 15:59:44 0x14B0 54003 dynpool DATACACHE STRIPES : 64
2010-05-11 15:59:44 0x14B0 54003 dynpool DATACACHE HASH LIST : 86024
2010-05-11 15:59:44 0x14B0 54003 dynpool DATACACHE head items : 10753
2010-05-11 15:59:44 0x14B0 54003 dynpool DATACACHE head item siz: 8
2010-05-11 15:59:44 0x14B0 54003 dynpool DATACACHE TASK QUEUE : 3672
2010-05-11 15:59:44 0x14B0 54003 dynpool DATACACHE taskq items : 153
2010-05-11 15:59:44 0x14B0 54003 dynpool DATACACHE taskq size : 24
2010-05-11 15:59:44 0x14B0 54003 dynpool DATACACHE CONTROLBLOCKS: 343936
2010-05-11 15:59:44 0x14B0 54003 dynpool DATACACHE num cblocks : 2687
2010-05-11 15:59:44 0x14B0 54003 dynpool DATACACHE cblock size : 128
2010-05-11 15:59:44 0x14B0 54003 dynpool DYNP_B20_DATACACHE : 27752448
2010-05-11 15:59:44 0x14B0 54003 dynDATA DYND_B20_DATACACHE : 171968
2010-05-11 15:59:44 0x14B0 53000 DATACACH Finish data cache restart
2010-05-11 15:59:44 0x14B0 53000 B*TREE LOB file directory restart successful
2010-05-11 15:59:44 0x14B0 7 FileDir File directory restarting
2010-05-11 15:59:44 0x14B0 8 FileDir File directory restart completed
2010-05-11 15:59:44 0x14B0 20061 Log History: 50 (50) files existing
2010-05-11 15:59:44 0x14B0 20064 Log History: all history files registered, GC is ready
2010-05-11 15:59:44 0x14B0 ERR 51080 SYSERROR -9407 unexpected error
2010-05-11 15:59:44 0x14B0 ERR 3 Admin Database state: OFFLINE
2010-05-11 15:59:44 0x14B0 ERR 20025 Admin + ACTIVATE is missing
2010-05-11 15:59:44 0x14B0 19651 CONNECT Connection released, T69
2010-05-11 15:59:44 0x14B0 19621 DBSTATE Shutdown kill requested
2010-05-11 15:59:44 0x840 ERR 7 Messages Begin of dump of registered messages
2010-05-11 15:59:44 0x840 ERR 8 Messages End of the message list registry dump
2010-05-11 15:59:44 0x840 19684 TASKING Tracewriter termination timeout: 1200 sec
2010-05-11 15:59:44 0x1788 20000 Trace Start flush kernel trace
2010-05-11 15:59:44 0x1788 19617 VOLUMEIO Single I/O attach, 'knltrace', UKT:1
2010-05-11 15:59:44 0x1788 20001 Trace Stop flush kernel trace
2010-05-11 15:59:44 0x1788 20002 Trace Start flush kernel dump
2010-05-11 15:59:44 0x1788 20003 Trace Stop flush kernel dump
2010-05-11 15:59:44 0x1788 19619 TASKING Releasing tracewriter
2010-05-11 15:59:44 0x840 19890 DIAGHIST Backup of diagnostic files will be forced at next restart
2010-05-11 15:59:44 0x840 19600 VERSION 'Kernel 7.6.06 Build 010-123-229-880'
2010-05-11 15:59:44 0x840 19654 DBSTATE SERVERDB 'S00' has stopped
I don't know what to do, help me please,
Thanks in advanced!
regards, ValentinaHello,
You got error:
u201C2010-05-11 15:59:44 0x14B0 ERR 20025 Admin + ACTIVATE is missingu201D
The reason could be that before you started the database online,
you tried to restore a backup with initialization and it failed, or tried
to initialize the database <db_activate > and failed.
-> Please check the dbm.prt & dbm.utl files when the database was activated last time.
Was the last step of the u201CCREATE INSTANCE WITH RESTOREu201D or u201CCREATE INSTANCE SYSDBA ..u201D successful? < If the step was successful, you will see in dbm.utl
u201CRETURNCODE 0;CREATE INSTANCE SYSDBAu201D after u201CCREATE INSTANCE SYSDBA..u201D, for example. >
-> Are you SAP customer?
Thank you & best regards, Natalia Khlopina
Maybe you are looking for
-
I have often had this problem - in previous versions of Keynote - where a file would open up with a warning that various image files could not be found, even though they had never been moved from their original location. This entailed reloading them
-
I bought several new songs, then went to my laptop to back it up. I unplugged my ipod only to find out that my new music does not work nor any old songs which I've had on my laptop that I've recently added to my ipod. This is extremely frustrating. I
-
Create a Puchase order using Bapi
Hi all, I have requirent to create a PO by using Bapi based on text file sent from interface system here with the file layout. 1.plant (ekko-werks) 2. material EKPO-MATNR 3. pur.group EKKO-EKGRP 4.vendor EKKO-LIFNR
-
Making a pdf of an InDesign Booklet
Ever since I installed Snow Leopard I have not been able to format InDesign booklets into a pdf. I have read many postings on this topic but nothing has worked so far. The best I have come up with is for me to de-install Snow Leopard and go back to L
-
Can I programmaticaly to change (to switch between two options) the color of ALL controls by some common command without dealing with property node of each control? Thank you, Boris