This is an old post I kept as draft 8 months before I published it…
This is a simple one, a reminder till next time I forget this, since stuff encountered after a Google-search led me astray…
The only reason to read this post is if you have googled for the error “ORA-00904: “POLTYP”: invalid identifier”. This error occurs if you try the old export command from an 11g client against a database on version 10g or lower. The export command runs a query against a table called EXU9RLS in the SYS schema. On 11g this table was expanded with the column POLTYP and the export command (exp) expects to find this column. This should not be much of a problem since Data Pump…
The following code is from a migration project I’m working on. It is part of a package named PERFORMANCE and is run every 15 minutes:
A simple implementation of Collatz conjecture in PL/SQL:
Not talking about a lost wallet with money, but the wallet used for encryption in the Oracle database and with encrypted backup.
If you have a lousy database model, you can get around it with triggers. If you need to hide some business logic from everybody else, you can do it with triggers. If you need a mechanism that bypass the consistency in the database, you can do it with triggers. They live a life on their own, seemingly autonomous from everything else and one easily forgets they exist. That is why I hate them. What matters if you do an database export in consistent mode if some active triggers make the data…
If your database is using anything else than UTF8 as database character set you may consider to migrate from it. Oracle states in the Globalization Guide (10gR2):
Using the CONVERT command in RMAN can be an efficient way to migrate a database from one OS to another, if they have the same endian.
Case: I wanted to reinstall the Enterprise Manager agent on a host. I went on to delete the host in the list of targets in EM. Then after a new installation and synchronization I somehow managed to push the list of targets from GC to the agent and thereby removing the host as a target in the local targets.xml file. Result: The monitored host did never show up in the target list of hosts even after a successful installation of the agent.
