Your point
1) The default for imp is "IGNORE=N", which directs the imp utility not to ignore the existence of a table you are attempting to import; it throws an error for that table...does not proceed with the import for that table, but proceeds to the next table.
But if the table exists it...
The problem was that the report run in production did not finish properly and as such the figures were different. The one on dev was OK.
As a matter of interest what option in import will force all the objects in the schema to be dropped and recreated. Obviously using drop <user> cascade prior...
Thanks.
Actually we do the following before import for this schema:
drop user bond cascade ;
So effectively all objects belonging to this schema are dropped prior to import. We then create this user and assign the appropriate profile. However, we found the proplem and is not related to...
I am importing an schema called bond from production to dev.
I use the following syntax:
imp system/password file=$PIPEFILE log=${IMPORT_LOG} fromuser=bond touser=bond;
The output from log shows no error:
. importing BOND's objects into BOND
. . importing table "ADDRESS"...
To summarize:
I connect to Oracle via SQLPLUS. I issue single line transaction via SQLPLUS. If I want to issue batched transactions (i.e. multiple SQL statement in one "BUSINESS UNIT" as you put it correctly), I will have to use PLSQL construct. That is the major difference between SQL*Plus and...
Santa,
IN SQLPLUS if I put all the below
select sysdate from dual;
update table a;
insert into table b;
select sysdate from dual;
in a file every line will be executed separetly and the result will be displayed per SQL statement. If one fails the other still goes through. However, if I...
Actually I just differentiate between these two as SQLPLUS being a command line language and PLSQL as block based development tool. You cannot have block based coding in SQLPLUS.
Thanks Again. Any tool which allows me to interact with Oracle in a batch format (allowing me to create SPs, functions and packages) as opposed to single line queries common with SQLPLUS I call it PL/SQL tool. The diffeence between two as I see it is that SQLPLUS is designed for single queries...
Thanks Dima.
My understanding is that a login to SQLPLUS or PL/SQL will be interpreted as an implicit start of transaction. You can put as many batch blocks in PL/SQL as you wish. They will not be commited unless you explicitely issue 'commit work' or 'rollback' However a DDL statement will be...
Thanks but that is not one batch. Because every line is executed separately. I gather the only way to do it will be in PL/SQL.
begin
select sysdate from dual;
update table a;
insert into table b;
select sysdate from dual;
end;
This will be one batch transaction. If one of the above DML...
Thanks I just gave an exampple. I do not particularly worry about the SQL in each line. What I want to know if it is possible to have three lines of SQL statement in SQLPLUS (Not PL/SQL) by doing the following:
select ... from abc;
update ... set ... where ...;
select sysdate from dual;
Can...
In PL/SQL I can do the following in a batch statement
1 declare v_num int := 0;
2 begin
3 select count(*) into v_num from test_frag where rownum < 100000;
4 update test_frag set big_column = big_column where rownum < 10;
5* end;
/
PL/SQL procedure successfully completed.
How...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.