J2EE failover HA OSS note 1085521 - startup with primary db2 unavailable

We have implemented J2EE HA failover solution according to OSS note 1085521.
We have an SAP system called SXD with primary db2 SXD1 and standy db2 SXDA. If JAVA is running against SXD1 and this Db2 subsystem is stopped/abends, then JAVA switches over to continue running on SXDA. However, if we then cycle the JAVA instance, it does not startup any more until we restart the primary SXD1 Db2 subsystem. Is this the way the design for the JAVA failover works, or do you think we must have an incorrect setting somewhere ?
The ABAP stack of the same SAP system works fine and can be restarted without problems even when the primary Db2 is stopped.

This problem is resolved after implementing latest 1085521 recommendations and upgrading to Db2 connect v9.5

Similar Messages

Dataguard configured using RMAN not in sync with Primary

Hi All.
I have configured physical standby using RMAN it has errored out as below message since the Physical standby is came in Mount state and it is not in sync with Primary.
$ rman target sys/oracle1@PROD_st_STBY auxiliary /
Recovery Manager: Release 11.2.0.1.0 - Production on Sun Jul 29 13:27:02 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: PROD_ST (DBID=609107922)
connected to auxiliary database: PROD_ST (not mounted)
RMAN> duplicate target database for standby dorecover;
Starting Duplicate Db at 29-JUL-12
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=156 device type=DISK
contents of Memory Script:
set until scn 239665;
restore clone standby controlfile;
executing Memory Script
executing command: SET until clause
Starting restore at 29-JUL-12
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /oracle1/oraerp/PROD_st/rman/07ngg1p6_1_1
channel ORA_AUX_DISK_1: piece handle=/oracle1/oraerp/PROD_st/rman/07ngg1p6_1_1 tag=TAG20120719T140110
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
output file name=/oracle1/oraerp/PROD_st/cont_.ctl
Finished restore at 29-JUL-12
contents of Memory Script:
sql clone 'alter database mount standby database';
executing Memory Script
sql statement: alter database mount standby database
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03002: failure of Duplicate Db command at 07/29/2012 13:27:29
RMAN-05501: aborting duplication of target database
RMAN-05001: auxiliary file name /oracle1/oraerp/PROD_st/undotbs1.dbf conflicts with a file used by the target database
RMAN-05001: auxiliary file name /oracle1/oraerp/PROD_st/sysaux.dbf conflicts with a file used by the target database
RMAN-05001: auxiliary file name /oracle1/oraerp/PROD_st/system01.dbf conflicts with a file used by the target database
RMAN>
SQL> select name,open_mode from v$database;
NAME OPEN_MODE
PROD_ST MOUNTED
SQL> select name,db_unique_name,database_role from v$database;
NAME DB_UNIQUE_NAME DATABASE_ROLE
PROD_ST PROD_st_STBY PHYSICAL STANDBY
SQL>
SQL> alter database recover managed standby database disconnect;
Database altered.
SQL>
SQL> alter system set log_archive_dest_state_2=enable;
System altered.
SQL> sho parameter log_archive_dest_2
NAME TYPE VALUE
log_archive_dest_2 string LOCATION=/oracle1/oraerp/PROD_
st/arch/ VALID_FOR=(ALL_LOGFIL
ES,ALL_ROLES)
On Primary
==========
SQL> SELECT THREAD# "Thread",SEQUENCE# "Last Sequence Generated"
FROM V$ARCHIVED_LOG
WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)
ORDER BY 1; 2 3 4
Thread Last Sequence Generated
1 281
ON STANDBY
SQL> SELECT ARCH.THREAD# "Thread", ARCH.SEQUENCE# "Last Sequence Received", APPL.SEQUENCE# "Last Sequence Applied", (ARCH.SEQUENCE# - APPL.SEQUENCE#) "Difference"
2 FROM
3 (SELECT THREAD# ,SEQUENCE# FROM V$ARCHIVED_LOG WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$ARCHIVED_LOG GROUP BY THREAD#)) ARCH,
4 (SELECT THREAD# ,SEQUENCE# FROM V$LOG_HISTORY WHERE (THREAD#,FIRST_TIME ) IN (SELECT THREAD#,MAX(FIRST_TIME) FROM V$LOG_HISTORY GROUP BY THREAD#)) APPL
5 WHERE
6 ARCH.THREAD# = APPL.THREAD#
ORDER BY 1; 7
no rows selected
SQL>
SQL> SELECT THREAD#, LOW_SEQUENCE#, HIGH_SEQUENCE# FROM V$ARCHIVE_GAP;
no rows selected
SQL>
Please suggest solution.
Best Regards,
Edited by: user13707876 on 19-Jul-2012 02:04

Hi,
It has worked now since error with warnings encountered as below:
$ rman target sys/oracle1@PROD_st_STBY auxiliary /
Recovery Manager: Release 11.2.0.1.0 - Production on Sun Jul 29 15:57:39 2012
Copyright (c) 1982, 2009, Oracle and/or its affiliates. All rights reserved.
connected to target database: PROD_ST (DBID=609107922)
connected to auxiliary database: PROD_ST (not mounted)
RMAN> duplicate target database for standby nofilenamecheck;
Starting Duplicate Db at 29-JUL-12
using target database control file instead of recovery catalog
allocated channel: ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: SID=156 device type=DISK
contents of Memory Script:
restore clone standby controlfile;
executing Memory Script
Starting restore at 29-JUL-12
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: restoring control file
channel ORA_AUX_DISK_1: reading from backup piece /oracle1/oraerp/PROD_st/rman/0enggc17_1_1
channel ORA_AUX_DISK_1: piece handle=/oracle1/oraerp/PROD_st/rman/0enggc17_1_1 tag=TAG20120719T165607
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:01
output file name=/oracle1/oraerp/PROD_st/cont_.ctl
Finished restore at 29-JUL-12
contents of Memory Script:
sql clone 'alter database mount standby database';
executing Memory Script
sql statement: alter database mount standby database
contents of Memory Script:
set newname for tempfile 1 to
"/oracle1/oraerp/PROD_st/temp01.dbf";
switch clone tempfile all;
set newname for datafile 1 to
"/oracle1/oraerp/PROD_st/system01.dbf";
set newname for datafile 2 to
"/oracle1/oraerp/PROD_st/sysaux.dbf";
set newname for datafile 3 to
"/oracle1/oraerp/PROD_st/undotbs1.dbf";
set newname for datafile 4 to
"/oracle1/oraerp/PROD_st/users01.dbf";
restore
clone database
executing Memory Script
executing command: SET NEWNAME
renamed tempfile 1 to /oracle1/oraerp/PROD_st/temp01.dbf in control file
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
executing command: SET NEWNAME
Starting restore at 29-JUL-12
using channel ORA_AUX_DISK_1
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00001 to /oracle1/oraerp/PROD_st/system01.dbf
channel ORA_AUX_DISK_1: restoring datafile 00004 to /oracle1/oraerp/PROD_st/users01.dbf
channel ORA_AUX_DISK_1: reading from backup piece /oracle1/oraerp/PROD_st/rman/09nggc0j_1_1
channel ORA_AUX_DISK_1: piece handle=/oracle1/oraerp/PROD_st/rman/09nggc0j_1_1 tag=TAG20120719T165547
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:03
channel ORA_AUX_DISK_1: starting datafile backup set restore
channel ORA_AUX_DISK_1: specifying datafile(s) to restore from backup set
channel ORA_AUX_DISK_1: restoring datafile 00002 to /oracle1/oraerp/PROD_st/sysaux.dbf
channel ORA_AUX_DISK_1: restoring datafile 00003 to /oracle1/oraerp/PROD_st/undotbs1.dbf
channel ORA_AUX_DISK_1: reading from backup piece /oracle1/oraerp/PROD_st/rman/08nggc0j_1_1
channel ORA_AUX_DISK_1: piece handle=/oracle1/oraerp/PROD_st/rman/08nggc0j_1_1 tag=TAG20120719T165547
channel ORA_AUX_DISK_1: restored backup piece 1
channel ORA_AUX_DISK_1: restore complete, elapsed time: 00:00:03
Finished restore at 29-JUL-12
contents of Memory Script:
switch clone datafile all;
executing Memory Script
datafile 1 switched to datafile copy
input datafile copy RECID=1 STAMP=789926299 file name=/oracle1/oraerp/PROD_st/system01.dbf
datafile 2 switched to datafile copy
input datafile copy RECID=2 STAMP=789926299 file name=/oracle1/oraerp/PROD_st/sysaux.dbf
datafile 3 switched to datafile copy
input datafile copy RECID=3 STAMP=789926299 file name=/oracle1/oraerp/PROD_st/undotbs1.dbf
datafile 4 switched to datafile copy
input datafile copy RECID=4 STAMP=789926299 file name=/oracle1/oraerp/PROD_st/users01.dbf
ORACLE error from auxiliary database: ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 1 thread 1: '/oracle1/oraerp/PROD_st/redo.log'
RMAN-05535: WARNING: All redo log files were not defined properly.
ORACLE error from auxiliary database: ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 2 thread 1: '/oracle1/oraerp/PROD_st/redo_2.log'
RMAN-05535: WARNING: All redo log files were not defined properly.
ORACLE error from auxiliary database: ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 5 thread 0: '/oracle1/oraerp/PROD_st/log5.log'
RMAN-05535: WARNING: All redo log files were not defined properly.
ORACLE error from auxiliary database: ORA-19527: physical standby redo log must be renamed
ORA-00312: online log 6 thread 0: '/oracle1/oraerp/PROD_st/log6.log'
RMAN-05535: WARNING: All redo log files were not defined properly.
Finished Duplicate Db at 29-JUL-12
RMAN>
So please suggest can i rename them all redolog file.
Best Regards,

Issue with physical standby database not in sync with primary

Hi,
I created an physical standby database couple of Hours back . I am trying to keep the standby database in Managed recovery mode to make the standby in sync with primary but it is throwing the below erros. Please share your suggestion ...
SQL> select thread#,max(sequence#) from v$log_history group by thread#;
THREAD# MAX(SEQUENCE#)
1 7
PROCESS STATUS THREAD# SEQUENCE#
ARCH CONNECTED 0 0
ARCH CONNECTED 0 0
RFS OPENING 1 12
ALERT LOG :
Tue Mar 20 07:31:32 2012
alter database recover managed standby database disconnect from session
Tue Mar 20 07:31:32 2012
Attempt to start background Managed Standby Recovery process (PRIMARY)
MRP0 started with pid=18, OS id=16370
Tue Mar 20 07:31:32 2012
MRP0: Background Managed Standby Recovery process started (PRIMARY)
Managed Standby Recovery not using Real Time Apply
parallel recovery started with 8 processes
Media Recovery Log /oracle/STDBY/arch/1_3_777567883.dbf
Tue Mar 20 07:31:39 2012
Completed: alter database recover managed standby database disconnect from session
Tue Mar 20 07:31:54 2012
Incomplete recovery applied all redo ever generated.
Recovery completed through change 9677325080303
Tue Mar 20 07:31:54 2012
MRP0: Media Recovery Complete (PRIMARY)
Tue Mar 20 07:31:55 2012
MRP0: Background Media Recovery process shutdown (PRIMARY)
Thanks,
Rakesh

HI CKPT,
Thanks for the reply. All the Archives from primary are transferred to the standby by RFS. Also i tried to register the log files manually even but it says already registered. They are no errors in the primary instance alert log file. Please find the log
SEVERITY ERROR_CODE MESSAGE TO_CHAR(TIMESTAMP,'D
Informational 0 ARC0: Archival started 20-MAR-2012 06:51:36
Informational 0 ARC1: Archival started 20-MAR-2012 06:51:36
Informational 0 ARC0: Becoming the 'no FAL' ARCH 20-MAR-2012 06:51:36
Informational 0 ARC0: Becoming the 'no SRL' ARCH 20-MAR-2012 06:51:36
Informational 0 ARC1: Becoming the heartbeat ARCH 20-MAR-2012 06:51:36
Informational 0 Redo Shipping Client Connected as PUBLIC 20-MAR-2012 06:52:07
Informational 0 -- Connected User is Valid 20-MAR-2012 06:52:07
Informational 0 RFS[1]: Assigned to RFS process 15934 20-MAR-2012 06:52:07
Informational 0 RFS[1]: Identified database type as 'physical standby' 20-MAR-2012 06:52:07
Warning 0 RFS[1]: No standby redo logfiles created 20-MAR-2012 06:52:07
Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 06:52:42
Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 06:52:42
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:52:47
Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 06:52:49
bf
Control 0 MRP0: Media Recovery Complete 20-MAR-2012 06:53:04
Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 06:53:06
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:53:24
Control 0 Media Recovery Complete 20-MAR-2012 06:53:43
Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 06:54:55
Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 06:54:55
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 06:55:00
Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 06:55:01
bf
Control 0 MRP0: Media Recovery Complete 20-MAR-2012 06:55:17
Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 06:55:18
Informational 0 Redo Shipping Client Connected as PUBLIC 20-MAR-2012 07:31:03
Informational 0 -- Connected User is Valid 20-MAR-2012 07:31:03
Informational 0 RFS[2]: Assigned to RFS process 16366 20-MAR-2012 07:31:03
Informational 0 RFS[2]: Identified database type as 'physical standby' 20-MAR-2012 07:31:03
Warning 0 RFS[2]: No standby redo logfiles created 20-MAR-2012 07:31:04
Warning 0 RFS[2]: No standby redo logfiles created 20-MAR-2012 07:31:06
Control 0 Attempt to start background Managed Standby Recovery process 20-MAR-2012 07:31:32
Control 0 MRP0: Background Managed Standby Recovery process started 20-MAR-2012 07:31:32
Informational 0 Managed Standby Recovery not using Real Time Apply 20-MAR-2012 07:31:37
Informational 0 Media Recovery Log /oracle/STDBY/arch/1_3_777567883.d 20-MAR-2012 07:31:38
bf
Control 0 MRP0: Media Recovery Complete 20-MAR-2012 07:31:54
Control 0 MRP0: Background Media Recovery process shutdown 20-MAR-2012 07:31:55
36 rows selected.
SQL> archive log list;
Database log mode Archive Mode
Automatic archival Enabled
Archive destination /oracle/STDBY/arch/
Oldest online log sequence 13
Next log sequence to archive 0
Current log sequence 14
SQL> ho ls -ltra /oracle/STDBY/arch/
total 3754456
drwxr-xr-x 4 oracle dba 4096 Feb 13 17:38 ..
-rw-r----- 1 oracle dba 908516864 Mar 20 06:37 1_8_777567883.dbf
-rw-r----- 1 oracle dba 770419200 Mar 20 06:40 1_3_777567883.dbf
-rw-r----- 1 oracle dba 757698048 Mar 20 06:41 1_4_777567883.dbf
-rw-r----- 1 oracle dba 5171712 Mar 20 06:41 1_5_777567883.dbf
-rw-r----- 1 oracle dba 1060801024 Mar 20 06:43 1_6_777567883.dbf
-rw-r----- 1 oracle dba 323025920 Mar 20 06:43 1_7_777567883.dbf
-rw-r----- 1 oracle dba 1558016 Mar 20 06:43 1_9_777567883.dbf
-rw-r----- 1 oracle dba 4608 Mar 20 06:43 1_10_777567883.dbf
-rw-r----- 1 oracle dba 1579008 Mar 20 06:52 1_11_777567883.dbf
-rw-r----- 1 oracle dba 11876864 Mar 20 07:31 1_12_777567883.dbf
-rw-r----- 1 oracle dba 2560 Mar 20 07:31 1_13_777567883.dbf
drwxr-xr-x 2 oracle dba 36864 Mar 20 07:31 .
SQL>

Standby not in sync with primary

Hi,
I am having oracle 9.2.0.7 on AIX and having physical standby database running on another server. Since the last 2 days it is not in sync and the required archivelog files are removed from production.
Could you please help me out to resolve the issue?
Thanx

Hi
Step 1 On the standby database, find the SCN which will be used for the incremental
backup at the primary database:
SQL> SELECT CURRENT_SCN FROM V$DATABASE;
Step 2 In RMAN, connect to the primary database and create an incremental backup
from the SCN derived in the previous step:
Step 3 RMAN> BACKUP INCREMENTAL FROM SCN <SCN from previous step>
DATABASE FORMAT '/tmp/ForStandby_%U' tag 'FORSTANDBY';
step 4 Transfer all backup sets created on the primary system to the standby system
SCP /tmp/ForStandby_* standby:/tmp
Step 5 Connect to the standby database as the RMAN target, and catalog all incremental
backup pieces:
RMAN> CATALOG START WITH '/tmp/ForStandby';
Step 6 Recover the standby database with the cataloged incremental backup:
RMAN> RECOVER DATABASE NOREDO;
Step 7 In RMAN, connect to the primary database and create a standby control file
backup:
RMAN> BACKUP CURRENT CONTROLFILE FOR STANDBY FORMAT '/tmp/ForStandbyCTRL.bck';
Step 8 Copy the standby control file backup to the standby system. For example:
SCP /tmp/ForStandbyCTRL.bck standby:/tmp
Step 9 Shut down the standby database and startup nomount:
RMAN> SHUTDOWN;
RMAN> STARTUP NOMOUNT;
Step 10 In RMAN, connect to standby database and restore the standby control file:
RMAN> RESTORE STANDBY CONTROLFILE FROM '/tmp/ForStandbyCTRL.bck';
Step 11 Shut down the standby database and startup mount:
RMAN> SHUTDOWN;
RMAN> STARTUP MOUNT;
Step 12 If the primary and standby database data file directories are identical, skip to step13. If the primary and standby database data file directories are different, then in
RMAN, connect to the standby database, catalog the standby data files, and switch
the standby database to use the just-cataloged data files. For example:
RMAN> CATALOG START WITH '+DATA_1/CHICAGO/DATAFILE/';
RMAN> SWITCH DATABASE TO COPY;
Step 13 If the primary and standby database redo log directories are identical, skip to step 14. Otherwise, on the standby database, use an OS utility or the asmcmd utility (if
it is an ASM-managed database) to remove all online and standby redo logs from
the standby directories and ensure that the LOG_FILE_NAME_CONVERT parameter
is properly defined to translate log directory paths. For example, LOG_FILE_
NAME_CONVERT=’/BOSTON/’,’/CHICAGO/’.
Step 14 On the standby database, clear all standby redo log groups (there may be more
than 3):
SQL> ALTER DATABASE CLEAR LOGFILE GROUP 1;
SQL> ALTER DATABASE CLEAR LOGFILE GROUP 2;
SQL> ALTER DATABASE CLEAR LOGFILE GROUP 3;
Step 15 On the standby database, restart Flashback Database:
SQL> ALTER DATABASE FLASHBACK OFF;
SQL> ALTER DATABASE FLASHBACK ON;
Step 16 On the standby database, restart MRP:
SQL> ALTER DATABASE RECOVER MANAGED STANDBY DATABASE DISCONNECT;
With this you can recvoer your Standby . I wish it will works for You.
Thanks
Karan

Logical Standby Database Not Getting Sync With Primary Database

Hi All,
I am using a Primary DB and Logical Standby DB configuration in Oracle 10g:-
Version Name:-
SQL> select * from v$version;
BANNER
Oracle Database 10g Enterprise Edition Release 10.2.0.5.0 - 64bi
PL/SQL Release 10.2.0.5.0 - Production
CORE 10.2.0.5.0 Production
TNS for Solaris: Version 10.2.0.5.0 - Production
NLSRTL Version 10.2.0.5.0 - Production
We have build the logical standby last week and till date the Logical DB is not sync. I have checked the init parameters and I wont see any problems with it. Also archive log destinations are also fine enough.
We have a important table named "HPD_HELPDESK" where record count is growing gradually whereas in logical standby it's not growing. There are some 19K record difference in the both the tables.
I have checked the alert log but it is also not giving any error message. Please find the last few lines of the alert log in logical Database:-
RFS LogMiner: Registered logfile [oradata_san1/oradata/remedy/arch/ars1_1703_790996778.arc] to LogMiner session id [1]
Tue Aug 28 14:56:52 GMT 2012
RFS[2853]: Successfully opened standby log 5: '/oracle_data/oradata/remedy/stbyredo01.log'
Tue Aug 28 14:56:58 GMT 2012
RFS LogMiner: Client enabled and ready for notification
Tue Aug 28 14:57:00 GMT 2012
RFS LogMiner: Registered logfile [oradata_san1/oradata/remedy/arch/ars1_1704_790996778.arc] to LogMiner session id [1]
Tue Aug 28 15:06:40 GMT 2012
RFS[2854]: Successfully opened standby log 5: '/oracle_data/oradata/remedy/stbyredo01.log'
Tue Aug 28 15:06:47 GMT 2012
RFS LogMiner: Client enabled and ready for notification
Tue Aug 28 15:06:49 GMT 2012
RFS LogMiner: Registered logfile [oradata_san1/oradata/remedy/arch/ars1_1705_790996778.arc] to LogMiner session id [1]
I am not able to trace the issue that why the records are not growing in logical DB. Please provide your inputs.
Regards,
Arijit

How do you know that there's such a gap between the tables?
If your standby db is a physical standby, then it is not open and you can't query your table without cancelling the recovery of the managed standby database.
What does it say if you execute this sql?
SELECT PROCESS, STATUS, THREAD#, SEQUENCE#, BLOCK#, BLOCKS FROM V$MANAGED_STANDBY;The ARCH processes should be connected and MRP waiting for a file.
If you query for the archive_gaps, do you get any hits?
select * from gv$archive_gapIf you're not working in a RAC environment you need to query v$archive_gap, instead!
Did you check whether the archives generated from the primary instance are transferred and present in the file system of your standby database?
I believe your standby is not in recovery_mode anymore or has an archive_gap, which is the reason why it doesn't catch up anymore.
Hope it helps a little,
Regards,
Sebastian
PS: I'm working on 11g, so unfortunately I'm not quite sure if the views are exist in 10gR2. It's worth a try though!
Edited by: skahlert on 31.08.2012 13:46

SPDD EHP4 Problems with DDIC modifications from OSS Notes

hi,
we made some ddic modifications (addes some fields to sap-tables accoring to oss-notes, also structures with .INCLUDE).
now in SPDD the system wants to create an Append Structure and it is impossible to just use the modifications as done accordingly to the oss notes?
can we accept the append-strucure proposal from spdd or should we throw the modifications away and redo it manually.
best regrards,
oliver

Hello Oliver,
Can you specify where exactly you are facing the problem.
You would have 2 options now :
1- Either to retain your modifications - adopt the modification
2. or overwrite everything by the corrections contained in the new SP - reset to original.
Both the above steps are independent and you can proceed as per your requirement. Absolutely
your and your team's choice.
Just in case you are not very much aware about SPDD or modification adjustments, review following:
http://help.sap.com/erp2005_ehp_04/helpdata/EN/2e/6d66587d9011d396b60000e82de14a/frameset.htm
Best Regards
niraj

OSS Notes for BI 7 Configuration.

Hi,
Bases configured BI 7 system ( First Time Client is SAP BI).I have checked the main T-Codes that we use in BI and everything is worki ng fine.
My point ,is there any OSS Notes that we need to implement while configuration BI 7?Be cause in mystem i am not able to see
any notes that are implemented ( Checked in SE10 & SNOTE T-codes).
If notes required what are they and what is the use of those notes?
Is there any other steps that I need to look into this.
Regards
Ram.
Edited by: Ramakanth Deepak Gandepalli on Jan 7, 2010 11:53 AM

Hi Ramakanth Deepa...,
If we update OSS note ,we can check the OSSnote in SAINT transaction code.
Let us see difference between Support pack and OSS Note.
Support Pack: SAP support pack contains many updates once with installation of support pack thse updates are updated into system , support pack can be check in SPAM transaction.
OSS Note: by comparing with support package ,OSS Note cantains minor updates,which will be applied to the system .once OSS note is applied. OSS can be check in SAINT transaction.
Hope this info may helps you.
Best Regards,
Maruthi

HOW TO CREATE SAP OSS NOTES ID

I am SAP FI certified and i have my certificate but i have only my SUID as written on certificate. now i want to create my OSS NOTES is , along with SUID i need to give password to create ID. please guide me how create oss id

Hi,
Login on sap market place then go to Data Administration------>User Data -
>Request new users.Then give authorization to this user.
Regards,
Pankaj

Help in finding an OSS notes for a SAP Program

Hi,
A runtime error TIME_OUT has occured in the program LSCD2F01.
I need to find an OSS notes which deals with the correction of this dump.I have checked with the latest date of modification of this program and it is 18.02.2006
So the OSS notes which has been generated earlier to this date has been implemented in the program.
I have attached the Dump details below: Any inputs on this will be helpful.
Information on where terminated
The termination occurred in the ABAP program "SAPLSCD1" in "READ_CD_FROM_DB".
 The main program was "SAPMSSY1 ".
 The termination occurred in line 1031 of the source code of the (Include)
 program "LSCD2F01"
 of the source code of program "LSCD2F01" (when calling the editor 10310).
Source Code Extract
1020 FORM read_cd_from_db CHANGING pt_cdhdr TYPE cdhdr_tab
1021 pt_cdpos TYPE cdpos_tab
1022 pt_cdpos_uid TYPE cdpos_uid_tab.
1023
1024 DATA: lt_cdhdr_for_uid TYPE cdhdr_tab
1025 ,lv_guid_true TYPE i.
1026 FIELD-SYMBOLS: <fs_cdhdr> TYPE cdhdr.
1027
1028 CLEAR: lt_cdhdr_for_uid[], lv_guid_true.
1029
1030 * select header from cdhdr
>>>> SELECT * FROM cdhdr INTO TABLE pt_cdhdr
1032 WHERE objectclas IN lt_sl_objectclas
1033 AND objectid IN lt_sl_objectid
1034 AND changenr IN lt_sl_changenr
1035 AND username IN lt_sl_username
1036 AND (
1037 (
1038 udate = date_of_change
1039 AND
1040 utime >= time_of_change
1041 )
1042 OR
1043 udate > date_of_change
1044 )
Regards,
Raj

Check notes:
459838 Performance improvement with very large datasets
and
671283 Performance problem with change documents material master
Rob

OSS Notes Implementation

Hi Experts,
Can anybody tell me the step to step procedure to see whether 50xxxxx OSS notes is already in the system or not.
If it is not implmented then how should I implement I mean what are the step involved.
I am using SRM 5.0 ECS....
Brgds
Gopesh

Hi Gopesh,
You can use transaction SNOTE for implementation of OSS note if there is program correctoion. OSS note release will with release version and Support pack of SRM. If your OSS note is release after your current version and SP#, then you have to implement it else note would be included for earlier releases.
For more detail,SRM_SERVER 5.0
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/spat/index.htm?sp1=SAPKIBKS09
( Note : Change SAPKIBKS09 to any needed SP number )
SRM_SERVER5.5
https://websmp230.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/spat/index.htm?sp1=SAPKIBKT08
( Note : Change SAPKIBKS08 to any needed SP number )
Regards,
Rahul Mandale

Identify OSS Notes Applied to J2EE Stack

We are running CRM 5.0 Netweaver CRM 5.0 2004s. We have applied several OSS Notes to the Java stack in DEV, QA, and PRD. Is there any way to determine which notes have been applied, short of re-applying the notes? Some of you may remember life before transaction SNOTE on the ABAP stack. The J2EE engine seems to be at that same stage, with no easy way to determine patches applied. Am I missing something?
Best regards,
Mike

Thanks Timo,
I realize there is no equivalent to SNOTE on the Java side, but is there any way to determine which notes have been applied, short of re-applying?
Take care,
Mike

Help with OSS Note Quality

Hi, I'm trying to review OSS Notes and I find a lot of notes that I feel don't have enough context to basically understand what the note is about. Basically I feel the Note Quality is poor. I found this one just today. Could someone look at it and let me know if they feel they understand this note or is it just me? Thanks!
[Note 1346134 - 0TCT_DS01 Deletion of statistical data|http://i34.tinypic.com/r0wa4h.png|Note 1346134 - 0TCT_DS01 Deletion of statistical data]

Hi Kenneth,
I'm also there with you. This is something needs to be reported to SAP and they have review this OSS note as the description that they have given is not proper.
There is some more information is missing. They are talking about the deletion of Statistical data from the table: RSDDSTAT_OLAP .... but they did not mentioned about the actual issue for which the correction has been applied..
Onlyway to understand is that correction code that they have which will give some idea but this note needs more information to assist all users......
Me I used to work on serveral notes but I did not come across this kind of note..
Anyway have a nice day...

Problem with OSS note

Hello. I do not know if there is anybody in here that has encountered this problem but....
We have NEW GL activated so we have to use transaction FAGL_FC_VAL with program FAGL_FC_VALUATION for closing year and converting some documents from local currency to other currencies.
When I run the program, there is a error concerning string length:
Runtime Errors READ_REPORT_LINE_TOO_LONG
Exceptn CX_SY_READ_SRC_LINE_TOO_LONG.
I have looked for a SAP note that corrects this error. I have implemented it but still...there is no effect. Suggestions?
The error takes place in K_KKB_FIELDCAT_MERGE function at line 366.
I do not thing that trimming the variable from 75 to 72 chars is a solution.
Thank you,
Cristian.

Hi. I have looked for OSS notes for this error. There is a note 1013501 that say this is an programming error and it can be fixed with correction instruction 844370 or install package SAPKH50016.
Still, after implementing the correction instruction, it didn't work.
For the moment I do not want to install packages.
My system is 5.0. Retail configuration.
Could you tell me the line numbers of that code?
Edited by: Cristian Boartes on Dec 21, 2007 4:01 PM

DP90 - Rebilling with down payment OSS Note 858703

Hello Gurus,
Even configuring customers test system according above mentioned OSS Note 858703 with order type TAF I do not get the process running.... When starting order creation (VA01) system doe not allow to enter sold-to and ship-to customer numbers.
This alone stops any testing.
Does anyone of you has experience or at least a clue what to do to resolve this? E.g. For testing I customized order type TA as ZTA and same same as order tpye TAF and it was possible to enter sold-to and ship-to party.
Any hind is very welcome as a customer waits for solution.
Many thanks in advance!!
Rgds, Carsten

Carsten
I just found out the reason why the system does not allow to enter sold-to and ship-to customer numbers:
"There is no partner determination procedure" assigned to order type TAF". This seems to be the way SAP delivers this order type.
So go there and assign whatever is the procedure you used for your other orders or create a new procedure and assign it, it will work fine.
By the way billling with down payment is not implemented at my customer site, I just tested with TAF order and it was behaving exactly as you described.
Then on a hunch I went and saw if there is a Partner Det procedure and there is none.
Path: SPRO/IMG/Sales and Distribution/Basic Functions/Partner Determination/Set Up Partner Determination and then
Set Up Partner Determination for Sales Document Header/Partner Determination Procedure Assignment
Hope this helps you, cheers.

Problem with OSS note 1529649 - Factory calendar expires 2010

Hi Experts,
I found a OSS note that is telling that calendar validity ends in 2010.
For the moment in my system factory calendar for all my sites is valid till 2020.
My question is that doesn't matter what date i have now in the system the validity will finish?
What i should do!!!
Thanks a lot for your help.

Dear
If the factory calender and holady calendar which is assinged in FC , both have same validity , then there should not be any problem .
For consistency , you can go down to OP03-Slecet HC-Change Mode -Keep the valaidty along with all the public holday calander validity till 2011 or 2012 .Similarly , do the same in Factory calander .
But re-assing the Calander to Plant once again in OP03 -Plant Assingent tab or re-assing at WC ( CR02-Capacity tab -Standard Avalaable Capacity ) also if you have similar kind of canalder also .
Hope this helps
Regards
JH
Edited by: Jiaul Haque on Dec 10, 2010 10:56 AM

J2EE failover HA OSS note 1085521 - startup with primary db2 unavailable

Similar Messages

Maybe you are looking for