Grant user access to several tables easy way

Hi, if you want to grant a database user access (insert, select, delete, update) to several tables of a view, you can use the following PL/SQL snippet:

Grant SELECT / INSERT / UPDATE rights to user for all tables in a schema

The following loop can be used to grant a user privileges for all tables of a schema:

PRFV-5637 DNS response time could not be checked on the following nodes

If you are getting following error on the installation of the Oracle Grid Infrastructure Installation:

PRFV-5637 DNS response time could not be checked on the fokllowing nodes
- Cause: An attempt to check DNS response time for unreachable node failed on nodes specified
- Action: Make sure that "nslookup" command exists on the nodes listed and the user executing the CVU check has execute privilege for it.

The problem is strongly related to the OS-level's bind-utils package.

The solution is to do the following as the root user:

After Grid Infrastructure deinstallation: [INS-40912] Virtual host name assigned to another system on the network

If you have ever installed a Oracle Grid Infrastructure Software and deinstalled it and again tried to install it, then you might run in the error [INS-40912] Virtual host name assigned to another system on the network.

If you check to ping node2 from node1 or node1 from node2 through their virtual IP's then that will succeed. This is wrong cause the nodes should NOT be pingable BEFORE the installation of the Grid Infrastructure.

In my case an alias was created for my interface NIC with the use of the virtual IP (which came with the previous installation):

eth0:2 Link encap:Ethernet  HWaddr 00:50:56:B9:0E:AA
       inet addr:10.200.11.159  Bcast:10.200.11.255  Mask:255.255.252.0
       UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
       Interrupt:19 Base address:0x2000

So in that case just do:

ifconfig eth0:2 down

Datafiles rausfinden, die Backup benötigen in sqlplus

Falls ihr irgendwann mal in der Situation seid, dass ihr rausfinden müsst, welche Datafiles ein Backup benötigen aber ihr aus irgendeinem Grund nicht RMAN benutzen könnt, dann könnt ihr folgenden Befehl in Sqlplus ausführen:

Apex ADMIN User/Benutzer ist gesperrt

Hallo,

letztens habe ich aus versehen in APEX meinen Admin User gesperrt wegen zu vielen falschen Versuchen. Ich war dabei verschiedene Lösungen dafür zu finden und das einfachste was ich finden konnte war folgendes:

1. Geht in eurer APEX Installations-Verzeichnis (normalerweise $ORACLE_HOME/apex)
2. Loggt euch in eure Datenbank ein via sqlplus as "sysdba"
3. Und dann folgendes ausführen: @apxchpwd

Das Script entsperrt den Admin-User und Ihr müsst dann einen neues Passwort speichern.

ORA-39095: Dump file space has been exhausted

Hi there,

when exporting database objects using DataPump, the objects are managed by DataPump in a .dmp file, which you specify with the dump file parameter in the expdp command:

dumpfile=FILENAME.dmp

Now with the exprt, the specified dump file will be created and will grow continuously as the export goes on. If your file system or any other setting limits the maximum allowed size for a file and the dump file reaches that limit and there are still objects remaining to be exported, you will get following error:

ORA-39095: Dump file space has been exhausted

The solution for that problem is that instead of creating one large dump file, create several smaller dump files and set a file size limit for the dump files:

Set the  maximum file size with the following parameter to your preferred value (in this case 1 GB):

filesize = 1000M

And now specify that if the file size limit is reached by the dump file, create the next dump file:

dumpfile=file_%U.dmp

where %U will by a number that will increment with each extra dump file that is created. In this case you would get dump files as followed:

file_1.dmp
file_2.dmp
file_3.dmp
...
file_99.dmp

Note that %U specification for the dump file can expand up to 99 files. If 99 files (99* 1GB = 99 GB) have been generated before the export has completed, it will again return the ORA-39095 error. So in that case you would have to increase the file size.