I have spent several hours finding the reason why installation of Oracle GoldenGate Veridata 12.2.1 on RedHad Enterpise Linux 7.3 starts correctly on one machine and doesn’t start on another – the same version and installed by the same administrator.
Starting installation just complains on X Server setup:
java -jar fmw_22.214.171.124.0_ogg.jar
Preparing to launch the Oracle Universal Installer from /tmp/OraInstall2017-03-30_10-47-55AM
X-Server access is denied on host
[Fatal Error] DISPLAY variable set incorrectly: localhost:11.0
[Resolution] Verify that your DISPLAY environment variable is set correctly,
and that there is an X11 server on the system. If you are
running the Oracle Installer as a different user or on a different host,
you may need to use the xhost command to ensure that host/user
has permission to write to your display
The most interesting thing is that starting already installed 126.96.36.199 GUI utils, like NETCA/DBCA/DBUA, works correctly… and they use the same X Server setup, actually through X Server Forwarding… because of this I have DISPLAY=localhost:11.0 Continue reading
Short note for myself on how to implement different RMAN Retention policies for DISK and TAPE backups in the same configuration.
The goal is to have:
- Retention for DISK backups as 7 Days;
- Retention for TAPE backups as 60 Days;
- set policy for TAPE as RMAN CONFIGURATION
- CONFIGURE RETENTION POLICY TO RECOVERY WINDOW OF 60 DAYS;
- for deletion of OBSOLETE backups use next commands as a single block:
- DELETE OBSOLETE DEVICE TYPE TAPE;
- DELETE OBSOLETE RECOVERY WINDOW OF 7 DAYS DEVICE TYPE DISK ;
From time to time (actually, once in a several years ;-)) I need to explicitly close opened database link, so here I’m putting some notes for myself on this topic.
Additionally to implicitly closing database link by closing you connection we have next methods for explicitly closing specific database link:
- ALTER SESSION CLOSE DATABASE LINK my_db_link;
- EXECUTE DBMS_SESSION.CLOSE_DATABASE_LINK(‘my_db_link‘);
What is the reasons and possible solutions for issue mentioned in subject ?
- indexes was created as NOPARALLEL at source database, so during import they will be creating with NOPARALLEL
- IMPDP wasn’t developed to create several indexes in parallel
- IMPDP BUGs, like this one – 8604502
Possible Solutions: Continue reading
Here I’m putting some example code on how to use SQLPatch for HINTing SQLs when it’s not possible to touch the application code or use other techniques to fix execution plan.
- work since 188.8.131.52
- are internally based on SQL Profiles;
- may be used to add HINTs to SQLs when you can’t touch code(like with Packaged Application);
- don’t require Diagnostics or Tuning Pack Licenses;
- sql text is normalized before storing, so additional spaces and case mismatch is not a problem;
- don’t handle SQL embedded literals, except through unpublished call to I_CREATE_SQL_PROFILE – see example later;
- RESULT_CACHE hint is honored since 184.108.40.206 and 12.2 – Check BUG:16974854;
- to check if SQL Profile was used add +NOTE when displaying execution plan
- SELECT * FROM table(dbms_xplan.display_cursor(format=>’+NOTE‘));
- to use HINTs with corrent syntax get them from desired execution plan:
- SELECT * FROM table(dbms_xplan.display_cursor(format=>’+OUTLINE‘));
Funny situation was discovered recently by one of our customers. Actually, it was an incident with Core Banking System, so, in reality, it wasn’t Funny….
I have checked and found that this issue reproduces not only with customer’s database using software version 220.127.116.11, but with version 18.104.22.168 with latest Oracle Database Proactive Bundle Patch(160719) installed.
To reproduce issue you need: Continue reading
Here I’ll describe some strange/interesting/ behaviour of Global Application Context connected with usage of Session Client Identifier, that is quite usually met in Application Express, J2EE Agent, Oracle Data Integrator starting from release 22.214.171.124 and many other applications that uses JDBC Connection Pooling in conjunction with setting Session Client Identifier.
So what is the problem ?
The problem is that Global Application Context doesn’t work as expected and described in documentation – attributes’ VALUES ARE NOT VISIBLE… Continue reading