New answers tagged

0

As per MOSC, this error can happen if the content of /etc/sysconfig/oracleasm is different across the nodes. The recommendations are: 1 - Make sure the file is the same on both nodes, and ORACLEASM_SCANORDER/ ORACLEASM_SCANEXCLUDE have the following content: ORACLEASM_SCANORDER="dm" ORACLEASM_SCANEXCLUDE="sd" 2 - Make sure the symbolic link is the same ...


0

Are the 37 indexes you have on the table global indexes? Option 1: Where you truncate and then rebuild This method is most appropriate if the partition that you are truncating has at least 10% of the total data in the table. But rebuilding these 37 indexes is going to take time. Option 2: Where you delete and truncate the partition The delete statement ...


0

To prevent that, just bypass the email and password option


0

The same issue I have just came across on CentOS 7. The installer form is disabled and does not allow any input. But clearly it is waiting for some input. In my case it is a GUI glitch. I was not able to find and resize any dialog. However, pressing Enter was enough to return focus to the main window. Though I can't really say what I confirmed or cancelled. :...


0

What OGG version are you using? Instead of DBA role, have you tried granting the required privileges through dbms_goldengate_auth.grant_admin_privilege? "Requirements When Configuring Extract or Replicat in Integrated Mode (Oracle) If using DBLOGIN to issue ADD EXTRACT, ALTER EXTRACT, or REGISTER EXTRACT to initiate integrated capture or ADD REPLICAT, ...


0

Assuming you are not using bigfile tablespaces and assuming you have no standard for how large datafiles should be or how empty they should be, you should create a tablespace with one 14G datafile and allow it to autoextend to a reasonable percentage of the overall free space you have available. If you have plenty of free space, you should set the maximum ...


3

You can try as below: SELECT name, LISTAGG(item_name, ' ') WITHIN GROUP (ORDER BY item_name) AS item_name FROM item GROUP BY name;


0

I got it to work with a weird fix : I removed the 'APPLICATION/APPLICATION@XE' and entered the username/password manually with the interactive prompt. I consulted this page: http://www.orafaq.com/wiki/Datapump and realized that I was not getting an equivalent of this line Connected to: Oracle Database 10g Enterprise Edition Release 10.2.0.1.0 - 64bit ...


0

First of all, DBA_SYNONYMS.SYNONYM_NAME is the name of the synonym. DBA_SYNONYMS.TABLE_NAME is the name of the object the synonym points to. In your query, it is not the synonym that is INVALID, but the object that it points to. It is not the synonym that needs to be fixed, but the object. If I try to recompile or drop these: ALTER PUBLIC SYNONYM ...



Top 50 recent answers are included