You missed some Downstream archived log?
Is this archived log on Downstream area either it’s not read by Logminer.
Try to run to the hills or read GrepOra posts.
In alert log is tracing like these:
ORA-00317: file type 0 in header is not log file
ORA-00334: archived log: '/oracle/dowstream-archive/2_136361_87643997.dbf'
LOGMINER: Error 317 encountered, failed to read corrupt logfile /oracle/dowstream-archive/2_136361_87643997.dbf
LOGMINER: Encountered error 1291 while adding logfile /oracle/dowstream-archive/2_136361_87643997.dbf to session 1
Copy the archived log from RMAN to Downstream, register logical logfile. Wait for while to Logimer start to provide LCR GoldenGate Integrated Extracts to Logminer new registered archived log.
Try register achived log on Dowstream database as below:
ALTER DATABASE REGISTER LOGFILE '/oracle/dowstream-archive/2_136361_87643997.dbf' FOR 'OGG$CAP_EXT_1';
ALTER DATABASE REGISTER LOGFILE '/oracle/dowstream-archive/2_136361_87643997.dbf' FOR 'OGG$CAP_EXT_2';
In an oracle fusion middleware environment, after migrate a metadata repository database to a new server or a new port, AdminServer failed after restart.
Caused By: oracle.security.jps.JpsException: oracle.security.jps.service.policystore.PolicyStoreException: javax.persistence.PersistenceException: Exception [EclipseLink-4002] (Eclipse Persistence Services – 2.5.2.v20140319-9ad6abd): org.eclipse.persistence.exceptions.DatabaseException
Internal Exception: java.sql.SQLRecoverableException: IO Error: The Network Adapter could not establish the connection
Error Code: 17002
####<Oct 18, 2017 8:09:27 PM BRST> <Notice> <WebLogicServer> <osb1grepora1> <AdminServer> <main> <<WLS Kernel>> <> <> <1508364567559> <BEA-000365> <Server state changed to FAILED.>
####<Oct 18, 2017 8:09:27 PM BRST> <Error> <WebLogicServer> <osb1grepora1> <AdminServer> <main> <<WLS Kernel>> <> <> <1508364567559> <BEA-000383> <A critical service failed. The server will shut itself down.>
####<Oct 18, 2017 8:09:27 PM BRST> <Notice> <WebLogicServer> <osb1grepora1> <AdminServer> <main> <<WLS Kernel>> <> <> <1508364567560> <BEA-000365> <Server state changed to FORCE_SHUTTING_DOWN.>
The files below have the physical address for the old configuration:
Look for the entry “jdbc.url” and change it with the new settings.
That’s all for today.
#Export ORACLE_SID of container DATABASE, – my Container DB is “cdb01”.
[oracle@greporalab]$ export ORACLE_SID=cdb01
[oracle@greporalab]$ sqlplus / as sysdba
#Change to CONTAINER’s ROOT session.
SQL> alter session set container=CDB$ROOT;
#Create user and ADD Roles.
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: