You could also use a trigger to get the info to a temp table as follows. This will probably fire after any error and could be performance hit. (happy new year to all).:
create or replace trigger system.server_1652_error_trig
after servererror
on database
declare
v_audsid number;
v_username
No.
The index should get used.Thequery result for query 2 is a subset of rows with ta.c1='val1' will get selected. Subset of query 1.
So there is no need for a full table scan.The index can be used in the following way :
1) Use index ind1 to get rows with ta.c1='val1' (which is query 1). This
One other disadvantage of putting all instances together is if you need to say bounce the database (for parameter change or other maintenanceetc) then all other applications will get affected. Whereas with separate instances other applications will not get affected.
To some extent one
I think data will never change like that. Are the owners the same. Or are you doing fromuser touser.
You can use the show option to see the contents of the export dumpfile. Then make sure all objects are dropped. [EMAIL PROTECTED] wrote:
I am 100% positive . I tried this process 2-3 times using
And synonyms will have to be re-created. (drop and create).
Grants will have to be given. Jared Still [EMAIL PROTECTED] wrote:
... and if your table is not partitioned, consider using'CREATE TABLE AS' with WHERE clause that eliminates the rows you wish to delete, recreate indexes and
The proc generates the 'exec dbms_stats ' statements for all the users. Are yousaving theoutput and running it manually or not.IT would have the same statements that you run one by one. Jose Luis Delgado [EMAIL PROTECTED] wrote:
List...SunOS 5.8, Oracle 8.1.6 (and 8.1.7 too).I use the proc at the
I assume both OS are same (Linux).
What you can do is rename the filenames using alter tablespace or alter database rename file. So
1) Copy database files, archive logs etc.to new machine
2) Startup mount
3)Rename files
4) Start recovery
You could also take a backup controlfile to trace then
