Streams propagation error

I have 2 Oracle 11.2 standard edition databases and I am attempting to perform synchronous capture replication from one to the other.
I have a propagation rule created with:
begin
DBMS_STREAMS_ADM.ADD_TABLE_PROPAGATION_RULES(
table_name => 'duptest.test1',
streams_name => 'send_test1',
source_queue_name => 'strmadmin.streams_capt_q',
destination_queue_name => '[email protected]',
include_dml => true,
include_ddl => false,
inclusion_rule => true);
end;
As stradmin on the source database I can query the streams_apply_q_table at orac11g.world (the destination database).
However the propagation fails and produces a job trace file stating:
kwqpdest: exception 24033
kwqpdest: Error 24033 propagating to "STRMADMIN"."STREAMS_APPLY_Q"
94272890B6B600FFE040007F01006D4C
Can anyone suggest what is wrong and how to fix this?

Paul,
The capture process is:
BEGIN
DBMS_STREAMS_ADM.ADD_TABLE_RULES(
table_name => 'duptest.test1',
streams_type => 'sync_capture',
streams_name => 'sync_capture',
queue_name => 'streams_capt_q');
END;
The apply process on the destination database is:
begin
dbms_apply_adm.create_apply(
queue_name => 'streams_apply_q',
apply_name => 'sync_apply',
apply_captured => false,
source_database => 'ORALIN1');
end;
begin
dbms_streams_adm.add_table_rules(
table_name => 'duptest.test1',
streams_type => 'apply',
streams_name => 'sync_apply',
queue_name => 'streams_apply_q',
include_dml => true,
include_ddl => false,
include_tagged_lcr => false,
source_database => 'ORALIN1',
inclusion_rule => true);
end;
There is an entry in the AQ$_STREAMS_CAPT_Q_TABLE_E table, and no entries in dba_apply_error or streams_apply_q_table so I am assuming that the message does not make it to the destination queue.
I have been assuming that the propagation and apply steps are independent. I.e. The apply queue separates the propagation activity from the apply activity. Is this wrong?
Thanks

Similar Messages

  • Propagation error

    how to clean up propagation error?
    1- Oracle version 9.2.0.1.0
    2-I have three instance bd1, bd2, bd3 in different machines
    3-The 3 instance can communicate between them via network.
    4-I have setup succefully streams environnement bidirectionally between the 3 databases
    5-I have tested it. and it works.
    7-I have a network disconnexion. When the connection is established my propagation display an error that the remote databases cannot be find. i have sopped then started the 3 instances but the propabgation still doesnt' work.
    I have never patched my Oracle.
    Could you help me plz?
    Thank you a lot dear members.

    after connexion establishment i have the following situation:
    bd1---> bd2 ok
    bd1---> bd3 ok
    bd2--->bd1 ok
    bd2--->bd3 ok
    bd3--->bd1 no
    bd3--->bd1 no
    i have used DBMS_AQADM.UNSCHEDULE_
    PROPAGATION in bd3--->bd1 and bd3----> bd2
    then restarted my 3 databases. so the bd3--->bd1 propagation errors dispeared. but bd3-----> bd2 errors still exist. and the propagations form bd3 to bd1 and bd2 don't work. i'm sure that i have no problem with TNS because i have tested my environment before discnnxion and it worked.

  • How to clean up propagation error?

    I have Asynchronous Distributed Hotlog CDC setup between a 9.2.0.8 (source) and 10.2.0.3 (staging) databases. There was a temporary lost of network connection between the two db and the source database is now reporting a ORA-12535 during propagation error.
    SQL> select instance, last_error_msg from dba_queue_schedules;
    1 ORA-12535: TNS:operation timed out
    The network is now ok but the error does not go away. How do I clean up the error to continue propagation w/o dropping and creating the entire change set?
    Thanks.

    If stop/start_propagation don't do it, then I would try using DBMS_AQADM.UNSCHEDULE_
    PROPAGATION and DBMS_AQADM.SCHEDULE_PROPAGATION
    See http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14258/d_aqadm.htm#CACDAABD
    PS: I have used it in 9i with succes. I recommend you try it in a test environment first.
    Regards,

  • DispatchKeyEvent propagation error

    Hi, I have a JDialog and there is at a certain moment a child modal JDialog. These 2 dialogs have this code
    public boolean dispatchKeyEvent(KeyEvent e)
    switch( e.getKeyCode() )
    case KeyEvent.VK_ESCAPE:
    cancelButton.doClick();
    return true;
    default:
    return false;
    so when the user press escape, it simulates a cancel operation. But the problem is that when the user press ESCAPE in the child dialog, the parent dialog also close. How can I stop the propagation of the key event so only the child dialog will close ?
    Thanks

    after connexion establishment i have the following situation:
    bd1---> bd2 ok
    bd1---> bd3 ok
    bd2--->bd1 ok
    bd2--->bd3 ok
    bd3--->bd1 no
    bd3--->bd1 no
    i have used DBMS_AQADM.UNSCHEDULE_
    PROPAGATION in bd3--->bd1 and bd3----> bd2
    then restarted my 3 databases. so the bd3--->bd1 propagation errors dispeared. but bd3-----> bd2 errors still exist. and the propagations form bd3 to bd1 and bd2 don't work. i'm sure that i have no problem with TNS because i have tested my environment before discnnxion and it worked.

  • Propagation error when trying to download inventory from server

    Hi there,
    Has anyone seen the following error when trying to download an inventory from the server.:
    Buildfile: C:\bea10.3\user_projects\workspaces\RST\RSTPropagation\21102009\propbuild.xml
    import:
    BUILD FAILED
    C:\bea10.3\user_projects\workspaces\RST\RSTPropagation\21102009\propbuild.xml:39: The propagation servlet returned a failure response: The [Download] operation is halting due to the following failure: null
    Additional Information:
    The propagation servlet returned the following log information found in [C:\DOCUME~1\myuser\LOCALS~1\Temp\onlineDownload__D21_H11_M8_S11.log]:
    INFO (Oct 21, 2009 11:08:11 AM SAST): Verbose logging has been disabled on the server.
    INFO (Oct 21, 2009 11:08:11 AM SAST): The propagation servlet is starting the [Download] operation.
    INFO (Oct 21, 2009 11:08:11 AM SAST): The modifier [allowMaintenanceModeDisabled] with a value of [true] will be used for this operation.
    INFO (Oct 21, 2009 11:08:11 AM SAST): Validating that current user is in the Admin role...SUCCESS
    ERROR (Oct 21, 2009 11:08:11 AM SAST): Validating that Maintenance Mode is enabled...FAILURE
    ERROR (Oct 21, 2009 11:08:11 AM SAST): Maintenance Mode has not been enabled on the server. With Maintenance Mode disabled it is possible for users to modify the application. This may cause problems for propagation.
    WARNING (Oct 21, 2009 11:08:11 AM SAST): Because the modifier [allowMaintenanceModeDisabled] was enabled this validation failure will be ignored and the operation will proceed. However, users will still be able to make modifications to the application, which could lead to missing data and unexpected propagation errors.
    WARNING (Oct 21, 2009 11:08:11 AM SAST): The temporary directory on the server used by propagation is [portal/bea10.3/user_projects/domains/RSTDomain/servers/wl_nstf/tmp/_WL_user/RSTEar/7v9j6d/public] with a length of [99] bytes. It is recommended that you shorten this path to avoid path length related failures. See the propagation documentation on how to specify the inventoryWorkingFolder context-param for the propagation servlet.
    INFO (Oct 21, 2009 11:08:19 AM SAST): Validating that LDAP and RDBMS security resources are in sync...SUCCESS
    INFO (Oct 21, 2009 11:08:19 AM SAST): Writing the inventory file to the servers file system at [{0}].
    ERROR (Oct 21, 2009 11:08:23 AM SAST): The [Download] operation is halting due to the following failure: null
    Total time: 14 seconds
    Please let me know if you have any ideas because "The [Download] operation is halting due to the following failure: null" means nothing to me.
    Please note changing the maintenace mode makes no difference.

    Please enable Verbose Logging on the propagation servlet
    http://download.oracle.com/docs/cd/E13155_01/wlp/docs103/prodOps/propToolAdvanced.html#wp1071690
    and check the logs on the server, they might give a clue

  • Stream closed error while testing a composite in EM

    HI,
    I have deployed a simple composite and wanted to test it in EM. I am getting a stream closed popup, not sure whats wrong?
    I have restarted the server and problem still persists.

    its actually remote server, I am able to deploy a simple HelloWorld composite and even able to see the same in Em.I can even browse through all the composites deployed there by many other people.But problem is when I try to test it its giving the Stream closed error.
    Is it something to do with access permissions, if so i would not have deployed it in first case..
    the pop up error message----
    Stream Closed
    For more information, please see the server's error log for
    an entry beginning with: Server Esception beginning with PPR, #14
    _______________________________

  • TT12241: Backup stream protocol error

    Hi there,
    I get the following error when replicating TT 6.04 datastore:
    $ /data/TimesTen/6.04/bin/ttRepAdmin -duplicate -from UsageCollector -host NODE_B -setMasterRepStart -delXla -localhost NODE_A UsageCollector
    TT12241: Backup stream protocol error: bad log data packet length -- file "restore.c", lineno 2865, procedure "restoreLogFileNS"
    Unfortunately this error, TT12241, is not described in the documentation. Oracle Support and Google searches don’t return any relevant information.
    Have any one came across this problem before?
    Thanks,
    Igor

    I can't find any previous SR reports of the TT12241. No probable candidate bugs are returned either. However I have not seen the -delXla option being used before, so it may have something to do with using this option. Are you able to exclude this option from the ttRepAdmin -duplicate, and allow the bookmarks to be copied over? You could then connect to the newly created datastore and try to manually delete the bookmarks using "xladeletebookmark".

  • PowerPivot 2012 Error: BaseWorkbook.CacheStream: Failed to read from stream. Error was: System.Data.SqlClient.SqlException: The EXECUTE permission was denied on the object 'proc_FetchChunkFromDocStreams', database 'SharePoint_AdminContent'

    Hi, I have setup PowerPivot 2012 for SharePoint, but when I access'PowerPivot Management Dashboard' in Central Admin I get error message 'An error has occured'
    Below is the error in the ULS,
    Background file fill operation caught exception: System.Data.SqlClient.SqlException: The EXECUTE permission was denied on the object 'proc_FetchChunkFromDocStreams', database 'SharePoint_AdminContent_ca021d58-ef1f-4f30-9aeb-6f24db24862b', schema 'dbo'.  
     at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)    
     at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)    
     at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)    
     at System.Data.SqlClient.SqlDataReader.ConsumeMetaData()    
     at System.Data.SqlClient.SqlDataReader.get_MetaData()    
     at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)    
     at System.Data.SqlClient.SqlCommand.CompleteAsyncExecuteReader()    
     at System.Data.SqlClient.SqlCommand.InternalEndExecuteReader(IAsyncResult asyncResult, String endMethod)    
     at System.Data.SqlClient.SqlCommand.EndExecuteReader(IAsyncResult asyncResult)    
     at Microsoft.SharePoint.CoordinatedStreamBuffer.AsyncSqlSession.EndExecuteReader(IAsyncResult ar)    
     at Microsoft.SharePoint.CoordinatedStreamBuffer.SPBackgroundSqlFileFiller.OnReadComplete(IAsyncResult result)
    BaseWorkbook.CacheStream: Failed to read from stream. Error was: System.Data.SqlClient.SqlException: The EXECUTE permission was denied on the object 'proc_FetchChunkFromDocStreams', database 'SharePoint_AdminContent_ca021d58-ef1f-4f30-9aeb-6f24db24862b',
    schema 'dbo'.    
     at Microsoft.SharePoint.CoordinatedStreamBuffer.SPBackgroundFileFiller.Fill()    
     at Microsoft.SharePoint.CoordinatedStreamBuffer.SPCoordinatedStreamBuffer.WaitForIntervalFill(SPInterval i)    
     at Microsoft.SharePoint.CoordinatedStreamBuffer.SPCoordinatedMemoryStream.Read(Byte[] array, Int32 offset, Int32 count)    
     at Microsoft.SharePoint.SPFileStream.Read(Byte[] buffer, Int32 offset, Int32 count)    
     at Microsoft.Office.Excel.Server.CalculationServer.BaseWorkbookManager.CacheStream(CachedFile cachedFile, FileLoader loader)
    Regards,
    Ayaz
    SharePoint Architect

    Hey Ayaz,
    I do had the same error message when I click on "PowerPivot Management Dashboard". After few research I resolved this issue.
    You need to provide the dbReader and dbWriter permission to powerpivot app pool account at "SharePoint_AdminContent_ca021d58-ef1f-4f30-9aeb-6f24db24862b"
    Have a great day :-)
    Santosh sethi

  • How to display propagation errors

    I have script to display apply errors and i would like to know if there is any scrip to display propagation errors because oracle tools like enreprise manager displays only the last error. Is there any script to display all propagation errors?( i use oracle 9.2.0.1)
    Thanks a lot.

    You could write a procedure to collect all propagation errors reported in catalog to your own history table. And run this procedure every couple of seconds using dbms_job to check for any errors in catalog.

  • TS3989 I keep getting this error when I click on the link inviting me to join a Photo Stream: "An error occurred while joining the Photo Stream. Please try again later. "

    I keep getting this error when I click on the link inviting me to join a Photo Stream: "An error occurred while joining the Photo Stream. Please try again later."
    I was the one who set up the Photo Stream and sent the link to myself. I called Apple and they said I did everything right and the server must be temporarily down, but it has been the same for the better part of a day.

    None of the fixes above worked for me.  Continued getting the "try again" error message. 
    Tryed a bunch of things, such as going directly to icloud on Safari to open the mail message, no luck.
    Tryed the following;
    Went to iCloud and logged in via Safari, clicked on my account name in top right corner, selected "Advanced" on drop down menu, and selected "Reset Photo Stream".
    Turned off Photo Stream on all devices and iPhoto.
    Turned on Shared Photo Stream option on Mac iCloud preferences.
    Tried the "Join This Photo Stream" button in my Mac Mail app .me account again.
    Still got the error message.
    Forwarded the original mail message to a yahoo account, selected "Join this Photo Stream" in the yahoo account mail (still in my Mac Mail app), and lo and behold, iPhoto opened and displayed the photos. 
    Could be this would have worked right from the start.
    Oh yea, still get the "try again" message if I click on the Photo Stream button in my .me account.

  • Endless "Stream Overlap" Error Loop Bug Crashes Encore

    Endless "Stream Overlap" Error Loop Bug Crashes Encore.
    This is the 4 th time I have reproduced the bug.
    I burn a Disk image .. and upon completion the "Disk Info" resets to zero bytes under the Build Menu and when checking the Timelines Window the Dialog Box pops up with the "Stream Overlap" Error.
    Has anyone else had this issue?
    I have read other forum post .. and there is nothing relevant.
    I had to rebuild the project twice from scratch.
    I'm waiting for my Master Collection 5.5 .. maybe it is fixed in it.

    NOTE: There is a issue with Premiere Pro Dynamically Linking with After Effects with file corrupting I am experiencing as well.
    Someone offered a solution to rename my files to just words. ( No numbers or other characters )
    It still crashes .. and there is still file corruption ... but a "Linked Composition" can be found by "Edit Original" .. whereas it was not found before I changed the filename.
    This is a beginning to find the source of the nested bugs.
    I am wondering if this filesystem problem is core to the "Stream Overlap" problem noted here.
    I have have not reached tech support on the Encore side of this problems as of yet.
    This type of file system also has a terrible result for dated files:
    On the Mac ( Standard Finder ) :
    2011.1.1
    2011.1.2
    2011.1.9
    2011.1.10
    2011.1.11
    is treated in Adobe Encore as well as other Adobe Suite Master Collection Apps ( On the Mac Platform ) as:
    2011.1.1
    2011.1.10
    2011.1.11
    2011.1.2
    2011.1.9
    This make NO logical sense at all .. and must be some old DOS filesystem?
    Timecode
    Datestamp
    Numbered Outlines
    Are all very important ways to organize files / video.
    I am surprised that Adobe did not address this years ago.
    I have had two Adobe users mention a file system problem that has been known.
    Maybe it is the cause of my issues? ... Adobe is mixing two incompatible filesystems on a root level on the Mac platform only. ( Doesn't work with the Mac Finder? )

  • Stream Write Error

    I am using the menu builder but I cannot save or preview
    anything. I get an error message that says "Stream Write Error".
    Captivate works fine.

    Hi gluckc
    Sorry, I really do wish I knew what to offer here. One other
    user reported this error and also has had no replies. Just in case
    something is discovered that answers the question or resolves the
    issue, I'm creating a cross link to that thread.
    Click
    here to view the other thread
    Cheers... Rick

  • Queue propagation error---ORA-23603

    Hi Experts,
    I got lots of error as ORA-23603: STREAMS enqueue aborted due to low SGA for Destination
    "STRMADMIN"."STREAMS_APPLY"@sale2.net.
    However, destination SGA taeget and Max as 2552M. and source target/Max SGA is 1888M.
    In source database EM, I saw these propagation and disable source capture and propagation.
    we use oracle 10gR4 in window 2003
    I check destination database, everything is ok without any error in there.
    What do I need to do? I can not start propagation and capture in sourec database.
    Thanks,
    Jim

    Thanks for you help. Actually, we set AQ_TM_PROCESSES as 1.
    I try to enable progation. but it does not work.
    I try to strat propagation and get error as
    SQL> begin
    2 DBMS_PROPAGATION_ADM.START_PROPAGATION(
    3 propagation_name=>'STREAM_PROPAGAT');
    4 end;
    5 /
    begin
    ERROR at line 1:
    ORA-01403: no data found
    ORA-06512: at "SYS.DBMS_PROPAGATION_INTERNAL", line 752
    ORA-06512: at "SYS.DBMS_PROPAGATION_ADM", line 145
    ORA-06512: at line 2
    SQL>
    SQL> show parameter AQ_TM_PROCESSES
    NAME_COL_PLUS_SHOW_PARAM TYPE
    VALUE_COL_PLUS_SHOW_PARAM
    aq_tm_processes integer
    1
    I saw EM Failures since startup 16. error as 20603. futhter check message tab. i got ORA-23603: STREAMS enqueue aborted due to low SGA in destination apply.
    However, I do not see any error for apply in destination DB.
    This is a bi_direction stream. From destion DB i also saw same message for source DB Apply issue. I can not find apply error in there too.
    What do I need to restart propagation? It is probation that DBA_propagation tanle that have error message ?
    Thanks for help!
    JIm

  • Helps for WLP9.2 in a cluster:  deploy errors, propagation errors

    I wrote a document for our portal project's production support that details how to fix several recuring problems with WLP9.2 (GA) in cluster. I'm sharing this with the community as a help.
    Email me if you'd like updates or have additional scenarios / fixes or you'd like the word doc version.
    Curt Smith, Atlanta WLP consultant, [email protected], put HELP WLP as a part of the subject please.
    1     WLP 9.2 Environment
    The cluster environment where these symptoms are frequently seen is described by the following:
    1.     Solaris 9 on 4 cpu sparc boxes. 16Gb Ram. The VM is given ?Xmx1034m.
    2.     Bea private patch: RSGT, fixed cluster deployments.
    3.     Bea private patch: BG74, fixed session affinity, changed the session tracking cookie name back to the standard name: JSESSIONID.
    4.     IBM UDB (DB2) using the Bea DB2 driver. FYI: the problems described below I don?t feel have any relationship to the DB used for a portal.
    2     Common problems and their fixes
    2.1     Failed deploy (Install) of a new portal application via the cluster console.
    Problem symptoms:
    After clicking Finish (or) Commit the console displays that there where errors. All errors require this procedure.
    Fix steps:
    1.     Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
    a.     Find the PID to kill: lsof ?C | grep <listen port number>
    b.     kill <pid>
    c.     Run kill again and if the pid is still running then do: kill -9 <pid>
    2.     Admin server:
    a.     Remove file: <domain>/config/config.lok
    b.     Edit file: <domain>/config/config.xml
    c.     Remove all elements of: <app-deployment> ? </app-deployment>
    d.     Start the Admin server
    e.     Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
    3.     Both Managed servers:
    a.     cd <domain>/config
    b.     rm ?rf *
    This forces the re-down load of the cleaned up config.xml.
    c.     cd <domain>/servers/<managed_name>
    d.     rm ?rf tmp cache stage data
    This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
    e.     Start each managed server.
    f.     Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
    You can now use the console to Install your applications.
    2.2     The portal throws framework / container exceptions on one managed instance.
    Problem symptoms:
    If you see exceptions from the classloader re a framework class not found, serialization failure or error etc. In general the symptom is that the container is not stable, running correctly, not making sense or your application works on one managed instance but not on the other.
    Fix steps:
    1.     Shut down the problem managed instance. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
    a.     Find the PID to kill: lsof ?C | grep <listen port number>
    b.     kill <pid>
    c.     Run kill again and if the pid is still running then do: kill -9 <pid>
    2.     Perform these clean up steps on one or both managed instances:
    a.     cd <domain>/config
    b.     rm ?rf *
    This forces the re-down load of the cleaned up config.xml.
    c.     cd <domain>/servers/<managed_name>
    d.     rm ?rf tmp cache stage data
    This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
    e.     Start each managed server.
    f.     Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
    3.     The libraries and applications should auto deploy as the managed instance comes up. Once the managed instance goes into the running state, or you Resume into the running state. Your application should be accessible. Sometimes it takes a few seconds after going into the running state for all applications to be instantiated.
    2.3     Content propagation fails on the commit step.
    Problem symptoms:
    In the log of the managed instance you specified in the propagation ant script you?ll see exceptions regarding not being able to create or instantiate a dynamic delegated role.
    There is an underlying bug / robustness issue with WLP9.2 (GA) where periodically you can?t create delegated roles either with the PortalAdmin or via the propagation utility.
    Important issue:
    This procedure was supplied by Bea which will remove from the internal LDAP and the portal DB your custom / created roles. This will leave your cluster in the new installation state with just the default users and roles: weblogic and portaladmin. The implications are that you?ll have to boot your cluster with console user: weblogic / weblogic. You can then add back your secure console user/password but you?ll have to do this over and over as propagations fail. The observed failure rate is once every 2-3 weeks if you do propagations daily.
    Note:
    The following assumes that you left the default console user weblogic password to be the default password of: weblogic. The following procedure deletes the local LDAP but leaves the rows in the DB.users table including the SHA-1 hashed passwords. The following procedure should still work if you changed the password for weblogic, but it probably won?t work if you try to substitute your secure console user/pw because there will be no delegated authorization roles mapping to your custom console user. You might experiment with this scenario.
    Fix steps:
    1.     Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
    a.     Find the PID to kill: lsof ?C | grep <listen port number>
    b.     kill <pid>
    c.     Run kill again and if the pid is still running then do: kill -9 <pid>
    2.     Admin server:
    a.     Remove directory: <domain>/servers/AdminServer/data/ldap
    b.     Run this SQL script after you edit it for your schema:
    delete from yourschema.P13N_DELEGATED_HIERARCHY;
    delete from yourschema.P13N_ENTITLEMENT_POLICY;
    delete from yourschema.P13N_ENTITLEMENT_RESOURCE;
    delete from yourschema.P13N_ENTITLEMENT_ROLE;
    delete from yourschema.P13N_ENTITLEMENT_APPLICATION;
    commit;
    c.     Start the Admin server
    d.     Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
    3.     Both Managed servers:
    a.     cd <domain>/servers/<managed_name>
    b.     rm ?rf data
    This forces the re-down load of the LDAP directory.
    c.     Start each managed server.
    d.     Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
    2.4     The enterprise portal DB fails and needs to be restored OR switch DB instances
    Restoring a portal DB or switching existing DBs are similar scenarios. The issues that you?ll face with WLP9.2 since it now uses a JDBCauthenticator to authenticate and authorize the console / boot user you need to first be able to connect to the DB before the admin and managed instances can boot. If you haven?t properly encrypted the DB user?s password in the <domain>/config/jdbc/*.xml files, then you?ll not be able to boot the admin server since you won?t be able to create a JDBC connection to the DB. The boot messages are not clear as to what the failure is.
    You?ll need to know an Admin role user and password that?s in the DB you?re wanting to connect to, to put into boot.properties and on the managed instances in their boot.properties or startManaged scripts. Don?t forget that the managed instances have local credentials which is new for 9.2. They are in the startManaged script in clear text or a local boot.properties.
    Note:
    The passwords in the DB are SHA-1 hashed and there is no SHA-1 hash generator tool so you can?t change a password via SQL, but you can move the password from one DB to another. This is possible because the domain encryption salt is not used to generate the SHA-1 string. As it turns out, the SHA-1 string is compatible with all 9.2 cluster domains. IE the domain DES3 salt has nothing to do with password verification. The same password SHA-1 string taken from different domains or even same domain but different users will be different, this is just a randomization put into the algorithm yet every domain will be able to validate the given password against the DB?s SHA-1 string. Because of this, I?ve not had any problem moving DB instances between clusters, especially if I?ve given up on security and use weblogic/weblogic as the console user and this user / pw is in every DB.
    Steps:
    The assumption for restoring a DB is that the DB has been restored but it?s an older version and doesn?t have the console user/pw that is in boot.properties. At this point swaping a DB is the same as restoring an old version of the portal DB.
    1.     Edit the console user and password as clear text into: <domain>/servers/AdminServers/security/boot.properties
    This is where you may give in and use weblogic/weblogic.
    2.     Set the correct DB access password encryption in the jdbc/*.xml files.
    a.     cd <domain>/bin
    b.     . ./setDomainEnv.sh or if you?re on windows just run: setDomainEnv.cmd
    c.     java weblogic.security.Encrypt <the_db_password>
    d.     Edit the returned string into every <domain>/config/jdbc/*.xml
    e.     Make sure the *.xml files point to the correct DB host, port, schema, DB name, DB user.
    3.     Start the Admin server. I should come up. If it doesn?t it has to be not being able to create a connection to the DB, which depends on the *.xml having the correct user and DES-3 encrypted password.
    4.     Edit the new console user/password on the managed instance bin/startManaged script or the local boot.properties.
    5.     Start the managed instances.
    2.5     Install patches on a host that does not have internet access
    The short description is to run smart update on a host that does have internet access. Fetch out of the <domain>/utils/bsu/cache_dir     directory the downloaded patch jar and xml. Manually apply the patch to your non-internet accessible hosts.

    I wrote a document for our portal project's production support that details how to fix several recuring problems with WLP9.2 (GA) in cluster. I'm sharing this with the community as a help.
    Email me if you'd like updates or have additional scenarios / fixes or you'd like the word doc version.
    Curt Smith, Atlanta WLP consultant, [email protected], put HELP WLP as a part of the subject please.
    1     WLP 9.2 Environment
    The cluster environment where these symptoms are frequently seen is described by the following:
    1.     Solaris 9 on 4 cpu sparc boxes. 16Gb Ram. The VM is given ?Xmx1034m.
    2.     Bea private patch: RSGT, fixed cluster deployments.
    3.     Bea private patch: BG74, fixed session affinity, changed the session tracking cookie name back to the standard name: JSESSIONID.
    4.     IBM UDB (DB2) using the Bea DB2 driver. FYI: the problems described below I don?t feel have any relationship to the DB used for a portal.
    2     Common problems and their fixes
    2.1     Failed deploy (Install) of a new portal application via the cluster console.
    Problem symptoms:
    After clicking Finish (or) Commit the console displays that there where errors. All errors require this procedure.
    Fix steps:
    1.     Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
    a.     Find the PID to kill: lsof ?C | grep <listen port number>
    b.     kill <pid>
    c.     Run kill again and if the pid is still running then do: kill -9 <pid>
    2.     Admin server:
    a.     Remove file: <domain>/config/config.lok
    b.     Edit file: <domain>/config/config.xml
    c.     Remove all elements of: <app-deployment> ? </app-deployment>
    d.     Start the Admin server
    e.     Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
    3.     Both Managed servers:
    a.     cd <domain>/config
    b.     rm ?rf *
    This forces the re-down load of the cleaned up config.xml.
    c.     cd <domain>/servers/<managed_name>
    d.     rm ?rf tmp cache stage data
    This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
    e.     Start each managed server.
    f.     Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
    You can now use the console to Install your applications.
    2.2     The portal throws framework / container exceptions on one managed instance.
    Problem symptoms:
    If you see exceptions from the classloader re a framework class not found, serialization failure or error etc. In general the symptom is that the container is not stable, running correctly, not making sense or your application works on one managed instance but not on the other.
    Fix steps:
    1.     Shut down the problem managed instance. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
    a.     Find the PID to kill: lsof ?C | grep <listen port number>
    b.     kill <pid>
    c.     Run kill again and if the pid is still running then do: kill -9 <pid>
    2.     Perform these clean up steps on one or both managed instances:
    a.     cd <domain>/config
    b.     rm ?rf *
    This forces the re-down load of the cleaned up config.xml.
    c.     cd <domain>/servers/<managed_name>
    d.     rm ?rf tmp cache stage data
    This cleans up stale or jammed sideways deploys. Be sure to delete all three directorys: tmp, cache, stage and data.
    e.     Start each managed server.
    f.     Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
    3.     The libraries and applications should auto deploy as the managed instance comes up. Once the managed instance goes into the running state, or you Resume into the running state. Your application should be accessible. Sometimes it takes a few seconds after going into the running state for all applications to be instantiated.
    2.3     Content propagation fails on the commit step.
    Problem symptoms:
    In the log of the managed instance you specified in the propagation ant script you?ll see exceptions regarding not being able to create or instantiate a dynamic delegated role.
    There is an underlying bug / robustness issue with WLP9.2 (GA) where periodically you can?t create delegated roles either with the PortalAdmin or via the propagation utility.
    Important issue:
    This procedure was supplied by Bea which will remove from the internal LDAP and the portal DB your custom / created roles. This will leave your cluster in the new installation state with just the default users and roles: weblogic and portaladmin. The implications are that you?ll have to boot your cluster with console user: weblogic / weblogic. You can then add back your secure console user/password but you?ll have to do this over and over as propagations fail. The observed failure rate is once every 2-3 weeks if you do propagations daily.
    Note:
    The following assumes that you left the default console user weblogic password to be the default password of: weblogic. The following procedure deletes the local LDAP but leaves the rows in the DB.users table including the SHA-1 hashed passwords. The following procedure should still work if you changed the password for weblogic, but it probably won?t work if you try to substitute your secure console user/pw because there will be no delegated authorization roles mapping to your custom console user. You might experiment with this scenario.
    Fix steps:
    1.     Shut down the whole cluster. Using Bea?s shutdown script takes too long, or doesn?t work if the Admin is down or hung.
    a.     Find the PID to kill: lsof ?C | grep <listen port number>
    b.     kill <pid>
    c.     Run kill again and if the pid is still running then do: kill -9 <pid>
    2.     Admin server:
    a.     Remove directory: <domain>/servers/AdminServer/data/ldap
    b.     Run this SQL script after you edit it for your schema:
    delete from yourschema.P13N_DELEGATED_HIERARCHY;
    delete from yourschema.P13N_ENTITLEMENT_POLICY;
    delete from yourschema.P13N_ENTITLEMENT_RESOURCE;
    delete from yourschema.P13N_ENTITLEMENT_ROLE;
    delete from yourschema.P13N_ENTITLEMENT_APPLICATION;
    commit;
    c.     Start the Admin server
    d.     Make sure it comes up in the running state. Use the console: servers ? admin ? control - resume if needed.
    3.     Both Managed servers:
    a.     cd <domain>/servers/<managed_name>
    b.     rm ?rf data
    This forces the re-down load of the LDAP directory.
    c.     Start each managed server.
    d.     Make sure the managed instance comes up in the running state and not admin. Go to server-<instance>-control-Resume to set the run state to running.
    2.4     The enterprise portal DB fails and needs to be restored OR switch DB instances
    Restoring a portal DB or switching existing DBs are similar scenarios. The issues that you?ll face with WLP9.2 since it now uses a JDBCauthenticator to authenticate and authorize the console / boot user you need to first be able to connect to the DB before the admin and managed instances can boot. If you haven?t properly encrypted the DB user?s password in the <domain>/config/jdbc/*.xml files, then you?ll not be able to boot the admin server since you won?t be able to create a JDBC connection to the DB. The boot messages are not clear as to what the failure is.
    You?ll need to know an Admin role user and password that?s in the DB you?re wanting to connect to, to put into boot.properties and on the managed instances in their boot.properties or startManaged scripts. Don?t forget that the managed instances have local credentials which is new for 9.2. They are in the startManaged script in clear text or a local boot.properties.
    Note:
    The passwords in the DB are SHA-1 hashed and there is no SHA-1 hash generator tool so you can?t change a password via SQL, but you can move the password from one DB to another. This is possible because the domain encryption salt is not used to generate the SHA-1 string. As it turns out, the SHA-1 string is compatible with all 9.2 cluster domains. IE the domain DES3 salt has nothing to do with password verification. The same password SHA-1 string taken from different domains or even same domain but different users will be different, this is just a randomization put into the algorithm yet every domain will be able to validate the given password against the DB?s SHA-1 string. Because of this, I?ve not had any problem moving DB instances between clusters, especially if I?ve given up on security and use weblogic/weblogic as the console user and this user / pw is in every DB.
    Steps:
    The assumption for restoring a DB is that the DB has been restored but it?s an older version and doesn?t have the console user/pw that is in boot.properties. At this point swaping a DB is the same as restoring an old version of the portal DB.
    1.     Edit the console user and password as clear text into: <domain>/servers/AdminServers/security/boot.properties
    This is where you may give in and use weblogic/weblogic.
    2.     Set the correct DB access password encryption in the jdbc/*.xml files.
    a.     cd <domain>/bin
    b.     . ./setDomainEnv.sh or if you?re on windows just run: setDomainEnv.cmd
    c.     java weblogic.security.Encrypt <the_db_password>
    d.     Edit the returned string into every <domain>/config/jdbc/*.xml
    e.     Make sure the *.xml files point to the correct DB host, port, schema, DB name, DB user.
    3.     Start the Admin server. I should come up. If it doesn?t it has to be not being able to create a connection to the DB, which depends on the *.xml having the correct user and DES-3 encrypted password.
    4.     Edit the new console user/password on the managed instance bin/startManaged script or the local boot.properties.
    5.     Start the managed instances.
    2.5     Install patches on a host that does not have internet access
    The short description is to run smart update on a host that does have internet access. Fetch out of the <domain>/utils/bsu/cache_dir     directory the downloaded patch jar and xml. Manually apply the patch to your non-internet accessible hosts.

  • Standard-Entreprise Propagation error remote DB

    Hello,
    I use a Oracle9i Release 9.2.0.1.0 - Production
    I create remotely queue tables and queues, propagation via DBLink. That's ok
    But the propagation fails with this error :
    ORA-02068: following severe error from REMTE
    ORA-00600: internal error code, arguments: [kolaHashFind:hash table], [], [], [], [], [], [], []
    Have any idear ?
    Thanks for info
    Regards
    Rafael Rimbert.

    we have found it.
    We transfert message wich payload is type sys.xmltype
    The problem was : one instance was with character set we8iso... and the other ms1252.

Maybe you are looking for