The following error occurs when I try to update a dbadapter or any other oracle apps adapter:
<BEA-149124> <Failures were detected while initiating deploy task for application “DbAdapter”. Error is: “There is the same running task 11 for DbAdapter#null”>
This error usually occurs when you are creating a new outbound connection with its respective plan.xml
Keep calm, you don’t have to redo the settings.
Do the following:
Activate the session, without updating the dbadapter or other oracle apps adapter that you were changing;
Create a new session in the weblogic console, update dbadapter and activate this session.
That’s all for today.
Now GoldenGate developments is easy friendly.
Cheers for Oracle Demo that include first mapping.
Oracle GoldenGate Studio Highligts:
- Separating Logical from the fisical
- One project contain many solutions
- A Solutions contain one logical design and many Physical Deployments
- You can AUTOMAP table mappings – drag and drop optional columns
- Easy deployments
- Easy to setup DB connections
This is simple right?
Some dev is forgetting to close the cursors. 🙂
If you don’t know what I’m talking about, I couldn’t find better reference than this article by Tech on the Net.
As DBA, we can identify the application schema which is causing the issue by the following: Continue reading
Oracle Service Bus 12.2 is now available to download on Oracle support.
It bring news to middleware admin and new features to developer.
Now, all user priviledges and group roles are managed by ‘EM Console’. So it would be little confusing in this release.
I had little inconvenince on first time that I triyed to use OSB with LDAP autorization.
After configure Weblogic in LDAP, user could login in Weblogic Console (/console)
But, can’t login Service Bus Console (/sbconsole), taking in browser http 401 (Unauthorized)
In WL Admin log:
[AdminServer] [ERROR] [ADFC-50017] [oracle.adfinternal.controller.application.AdfcExceptionHandler] [tid: [ACTIVE].ExecuteThread: '20' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: maiquel_oliveira] [ecid: fdf185a3-35fd-4171-9b75-4b80a0f40b03-000000cf,0] [APP: service-bus] [partition-name: DOMAIN] [tenant-name: GLOBAL] [DSID: 0000Lu77u7K7q2r6wJAhMG1Pj34E000001] ADFc: While attempting to handle this exception the application's exception handler failed.[[
oracle.adf.controller.security.AuthorizationException: ADFC-0619: Authorization check failed: User 'user_name' does not have 'VIEW' permission on 'jsf.resourcesPageDef'.
From RFC 2068 Hypertext Transfer Protocol — HTTP/1.1:
10.4.2 401 Unauthorized
The request requires user authentication. The response MUST include a WWW-Authenticate header field (section 14.46) containing a challenge applicable to the requested resource. The client MAY repeat the request with a suitable Authorization header field (section 14.8). If the request already included Authorization credentials, then the 401 response indicates that authorization has been refused for those credentials. If the 401 response contains the same challenge as the prior response, and the user agent has already attempted authentication at least once, then the user SHOULD be presented the entity that was given in the response, since that entity MAY include relevant diagnostic information. HTTP access authentication is explained in section 11.
Follow the trick:
Are you having notifications like this one from you ASR?
ALERT: Oracle Auto Service Request (ASR) has detected a heartbeat failure for these assets.
[list with "Serial"; "Hostnam"; "Information" of affected targets]
IMPACT: ASR would not be able to create a Service Request (SR) if a fault were to occur.
ACTION: Determine why the heartbeat has failed for these assets and resolve the issue.
This is only a notification saying that ASR not able to reach a target.
For detailed information on how to troubleshoot, you can access MOS Oracle Auto Service Request (ASR) No Heartbeat Issue – How to Resolve (Doc ID 1346328.2)
In general why, things to test are:
– Access from ASR server to transport.oracle.com, via https, using port 443.
– Access from ASR server to ASR assets, via http, using port 6481.
After installation of soa-infra or osb, in the first time the the managed server starts, the error occurs:
#### <[ACTIVE] ExecuteThread: '0' for queue: 'weblo gic.kernel.Default (self-tuning)'> <> <> <> <1478002511204>
Just edit the nodemanager.properties file that is inside the $WL_HOME/common/nodemanager.
Find the line with the content “StartScriptEnabled=false” and replace to “StartScriptEnabled=true”
If do you prefer, just run the command:
sed -i ‘s/StartScriptEnabled=false/StartScriptEnabled=true/g’ $WL_HOME/common/nodemanager/nodemanager.properties
AYE! GoldenGate 12.3 is now released!
What it brings?
– Support for Oracle Database 188.8.131.52
– Microservices Architecture
– Parallel Replicat
– Automatic Conflict-Detection-Resolution (CDR) without application changes
– Procedural Replication to enable simpler application migrations and upgrades
– Database Sharding
– Fast Start Capture
Let’s test this new features 🙂