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.

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

ACC Setup Error - Remote Server not Responding in the Proper Manner - Windows 7 Pro

Hello -
I was able to install the CC upgrades to all my software on my laptop without issue. Whenever I try to upgrade them on my desktop I recieve the attached error. I am running Windows 7 Professional. My guess this is being caused my my company's firewall however my IT director claims he set me up to bypass the firewall when trying to install this.
Thank you for your help.

Hi Mike603,
Please refer to the following help document on error " Remote Server not responding".
http://helpx.adobe.com/creative-suite/kb/remote-server-responding-installing-aam.html
Hope this helps.
Please let me know in case of any problem.
Regards,
Sumit Singh

Standard report s_ahr_61015512 .,., error

When i run the standard report s_ahr_61015512 .,., error message (Unsolicited application group 0001 does not exist) is coming how can i clear this error

SPRO
Personnel Management u2013 Recruitment u2013IMG Applicant Administration u2013 Applicant Structure u2013 Create Applicant Groups.
Applicant group Applicant Group text Applicant class Applicant class text
1 Active External AP External applicant
2 Active internal P Internal applicant
3 Student employee AP External applicant
4 Temporary Worker AP External applicant
Personnel Management u2013 Recruitment u2013 Applicant Administration u2013IMG Applicant Structure u2013 Create Applicant Ranges.
1 Trainee
2 Salaried Employees
3 Managerial Staff
Personnel Management u2013 Recruitment u2013 Applicant Administration u2013IMG Applicant Structure - Create Unsolicited Application Groups.
Unsoli Appl Unsol ApplicationGroup Administrator Administrator Name
001 Acounting dept. SCH Egon Schulz
002 Sales & distribution MEI Hans Meier
003 Personnel dept. MEI Hans Meier
004 Development SCH Egon Schulz
and assign NUAMP with applicant grp and ranges

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.

Standard Run Time Errors

Hello All,
With regard to Standard Run Time errors, say SUM_OVERFLOW, where do we get the documentation about this error(as well as erors of this type)
1. Dump analysis ST21 and the other that strikes me is the 2. OSS
Do correct me if i am wrong and please provide me further information.
TQ
- Sravan

Hi,
the ABAP keyword documentation offers a full text search.
If you enter SUM_OVERFLOW, you learn that this exception is raised from the SUM statement in a loop over an internal table.
Regards,
Horst

Getting an error "Remote Access Service Error" while establishing the connection usng SonicWall Netextender.

* Original Title: SonicWall Netextender issue with Windows 8.1
I am able to install SonicWall Netextender version 6.0.181 without any issues in my Windows 8.1 machine. When i try to establish the connection getting this error "Remote Access Service Error - Rebooting might Solve the problem".
Hope someone can help me in resolving this issue.

Hi,
Please go to Windows Service manager, run "services.msc", then Look for the Remote Access Auto Connection Manager and Remote Access Connection Manager to see if those two services have been started. If not, set them to automatic start, reboot the machine,
and install\configure NetExtender again.
Since this is a third party application, it's recommended to contact the application vender to check the compatibility with Windows 8.1\IE 11, because they're more familiar with the application.
http://help.mysonicwall.com/sw/eng/2605/ui2/1000/Admin/SSL-VPN_2000_1.0_Admin-8-1.html
NOTE
This response contains a reference to a third party World Wide Web site. Microsoft
is providing this information as a convenience to you. Microsoft does not control these sites and has not
tested any software or information found on these sites.
Yolanda Zhu
TechNet Community Support

Indesign standard version installation error for Mac OS: "installer failed to initialize.

Indesign standard version installation error for Mac OS: "installer failed to initialize. Please download Adobe Support Advisor to detect problem". Transferred by application over to new laptop, application considered damaged, with instructions to reinstall. Attempting from downloaded file.

go to HD>library>application support>adobe>caps and rename the caps folder.
go to USER library>application support>adobe>OOBE and rename OOBE folder
install Adobe application manager from below link.
http://www.adobe.com/support/downloads/detail.jsp?ftpID=4774

After a licensing failure message, I tried to reinstall CS3 design standard but the error "Component Install Failed" occurred and I still am unable to use Photoshop or InDesign Please Help!

after a licensing failure message, I tried to reinstall CS3 design standard but the error "Component Install Failed" occurred and I still am unable to use Photoshop or InDesign Please Help!

J3liu1 I would recommend reviewing the installation log files for the specific error message which you are facing. You can find details on how to locate an interpret your installation log files at Troubleshoot installation with install logs | CS3, CS4. You are welcome to post any specific errors you discover to this discussion.

Standard I/O error window popup

hello :
I am facing with a desperate trouble. I have completed the program code and ".uir" design, and when I Compile and execute them, there is no error appear, however when bringing datas and processing them use it, it would popup a standard I/O error window . what's wrong with them?
hopping for your answer.

CVI can use a console (sort of command prompt window) to output messages from specific functions. This console is called Standard I/O window and is exactly the one you are seeing running your app. Now, printf () is the most probable cause of this window to appear, but there are several other instructions that can cause this to happen: this old knowledgebase article lists some of them. You may check if your app is using any of them.
Standard I/O behaviour can be modified: see this document for reference; look also SetStdIOWindowOptions () command. Consider also this forum thread, which can be useful if calls to those functions is included in some external library you are using that you cannot modify.
Proud to use LW/CVI from 3.1 on.
My contributions to the Developer Zone Community
If I have helped you, why not giving me a kudos?

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.

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

Standard-Entreprise Propagation error remote DB

Similar Messages

Maybe you are looking for