Next Entend (Tablespace)

Hi
When a datafile in autoextend ON , does next extend with same size as the database block size is good for performance ?
Suppose my datafile is of 100Mb and extoextend on with next as 16K , and if i import a 2GB table in this datafile using imp i think the performance is very low . So increasing the next to a higher number like 100M is a good idea ?

avramits wrote:
checkpoint and SCN number for old files and complete information when new file created. Well, correct me if I am wrong, are you talking about "File Checkpoint"?I understand that with a new file, the info about it would be recorded but I am still in doubt about the statement that OP made when an extent is allocated , control file is updated? I checked in the V$sysstat but I couldn't find anything relevant which should match this. Tehre is indeed a File Checkpoint which does happen and is specific to a particular file only. And what about sCN? Wehre is SCN coming into the picture here ?
Regards
Aman....

Similar Messages

How to calculate AUTOEXTEND ON NEXT in tablespace clause

hi
Please explain How to calculate AUTOEXTEND ON NEXT in tablespace clause.
whether AUTOEXTEND ON NEXT 50M or 100M or 500M
Thanks

174313 wrote:
hi
Please explain How to calculate AUTOEXTEND ON NEXT in tablespace clause.
whether AUTOEXTEND ON NEXT 50M or 100M or 500M
ThanksThe autoextend size depends on the following :-
1) Tablespace type Dictionary managed (DMT) or Locally managed (LMT)
2) Segment space management manual or Auto.
3) Extent allocation management Autoallocate or uniform.
If your tablespace is Locally managed with segment management Auto (ASSM) and with extent management is uniform , the autoextend size will be uniform for all the extents , initial and next extents all will be uniform size .
If your tablespace is Locally managed with segment management Auto (ASSM) and with extent management is autoallocate, Oracle will size the extents automatically starts with 64KB and can go upto 64MB.
If you have dictionary managed tablespace you will specify the next size at tablespace creation.
Hope this helps.

Dropping tablespace for a partitionned table

Hi all,
I have a table partitionned and I want to drop the tablespace for a specific partition. So what happen in the table if I drop one tablespace with a commande drop tablespace tbs including contents and datafiles;
Does the index unusable in this table?
Regards

No, you can not drop a tablespace which contains tables whose partitions are not completely contained in this tablespace.
db9i :SQL> create tablespace users2 datafile '/u02/oradata/db9i/users201.dbf' size 10M;
Tablespace created.
db9i :SQL> CREATE TABLE sales_by_region (item# INTEGER, qty INTEGER,
2 store_name VARCHAR(30), state_code VARCHAR(2),
3 sale_date DATE)
4 STORAGE(INITIAL 10K NEXT 20K) TABLESPACE test
5 PARTITION BY LIST (state_code)
6 (
7 PARTITION region_east
8 VALUES ('MA','NY','CT','NH','ME','MD','VA','PA','NJ')
9 STORAGE (INITIAL 20K NEXT 40K PCTINCREASE 50)
TABLESPACE users,
10   11 PARTITION region_west
12 VALUES ('CA','AZ','NM','OR','WA','UT','NV','CO')
13 PCTFREE 25
14 TABLESPACE users2,
15 PARTITION region_unknown
16 VALUES (DEFAULT)
17 TABLESPACE test
18 );
Table created.
db9i :SQL> insert into sales_by_region values (1, 100, 'store 1','NY',sysdate);
1 row created.
db9i :SQL> insert into sales_by_region values (2, 200, 'store 2','UT',sysdate);
1 row created.
db9i :SQL> insert into sales_by_region values (3, 300, 'store 3','ZZ',sysdate);
1 row created.
db9i :SQL> commit;
Commit complete.
db9i :SQL> select count(*) from sales_by_region
2 /
COUNT(*)
         3
--insure all data went to the right partition
db9i :SQL> alter table sales_by_region truncate PARTITION region_east;
Table truncated.
db9i :SQL> select count(*) from sales_by_region
2 /
COUNT(*)
         2
db9i :SQL> alter table sales_by_region truncate PARTITION region_west;
Table truncated.
db9i :SQL> select count(*) from sales_by_region
2 /
COUNT(*)
         1
db9i :SQL> alter table sales_by_region truncate PARTITION region_unknown;
Table truncated.
db9i :SQL> select count(*) from sales_by_region
2 /
COUNT(*)
         0
db9i :SQL> insert into sales_by_region values (1, 100, 'store 1','NY',sysdate);
insert into sales_by_region values (2, 200, 'store 2','UT',sysdate);
insert into sales_by_region values (3, 300, 'store 3','ZZ',sysdate);
1 row created.
db9i :SQL>
1 row created.
db9i :SQL>
1 row created.
db9i :SQL>
db9i :SQL>
db9i :SQL> commit;
Commit complete.
db9i :SQL> select count(*) from sales_by_region
2 /
COUNT(*)
         3
--now drop one tablespace
db9i :SQL> drop tablespace users2 including contents and datafiles
2 /
drop tablespace users2 including contents and datafiles
ERROR at line 1:
ORA-14404: partitioned table contains partitions in a different tablespace
db9i :SQL> !oerr ora 14404
14404, 00000, "partitioned table contains partitions in a different tablespace"
// *Cause: An attempt was made to drop a tablespace which contains tables
//         whose partitions are not completely contained in this tablespace
// *Action: find tables with partitions which span the tablespace being
//          dropped and some other tablespace(s). Drop these tables or move
//          partitions to a different tablespace
--move table partition from users2 to users
db9i :SQL> alter table sales_by_region move partition region_west
tablespace users; 2
Table altered.
--drop tablespace again
db9i :SQL> drop tablespace users2 including contents and datafiles
2 /
Tablespace dropped.

Undo tablespace keeps growing

Hello,
my undotbs is growing 14g (although i my undotbs actul size is 9g) I try to resize datafiles, but
this may not work.
So, i am assuming to perform this task
>
- Create a new undo tablespace as :
SQL> create undo tablespace UNDOTBS2 datafile '<complete file path>' size <smaller size>;
- Change parameter UNDO_TABLESPACE
SQL> alter system set UNDO_TABLESPACE=UNDOTBS2;
- Drop UNDOTBS1
SQL> drop tablespace UNDOTBS1 including contents and datafiles;>
but my question is , is it worthy to delete the undotbs1 whose having alot of data and if i deleted
this (undotablespace) data ,i will not able to recover it thoroughly?
db_version:10.2.0(linux)

sunny kichlooIf your concern is regarding how to resize Refer this thread
>
i have already try this but it still growing and day-today we are running large transaction on our db.
marcopb Try to investigate why your undo tablespace is growing... and think about why your next undo tablespace won't grow as the previous...
>
our db size is 60g and we are running on heavy transection on it (everday)

Trying to understand rollback segments - offline tblspaces for backup

Using Oracle 8i, on Windows platform - The question - receive an error ORA-01556 when performing a
sql "ALTER TABLESPACE MY_TBS_LT OFFLINE IMMEDIATE";
=============================================
First off I created a tablespace and table on an 8i database.
create tablespace my_tbs_lt_tbs_lt
datafile '&&2\oradata\&&1\my_tbs_lt_guitest1.dbf'
size 10M
AUTOEXTEND ON NEXT 1280k EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K; <===== Is this right for use with rollback segments?
CREATE ROLLBACK SEGMENT rbgui1t2 STORAGE(INITIAL 50K NEXT 250K)
tablespace my_tbs_lt;
CREATE ROLLBACK SEGMENT rbgui2t2 STORAGE(INITIAL 50K NEXT 250K)
tablespace my_tbs_lt;
CREATE ROLLBACK SEGMENT rbgui3t2 STORAGE(INITIAL 50K NEXT 250K)
tablespace my_tbs_lt;
CREATE ROLLBACK SEGMENT rbgui4t2 STORAGE(INITIAL 50K NEXT 250K)
tablespace my_tbs_lt;
-- Bring new rollback segments online
ALTER ROLLBACK SEGMENT rbgui1t2 ONLINE;
ALTER ROLLBACK SEGMENT rbgui2t2 ONLINE;
ALTER ROLLBACK SEGMENT rbgui3t2 ONLINE;
ALTER ROLLBACK SEGMENT rbgui4t2 ONLINE;
CREATE TABLE guitester.guitester_t2
( employee_id NUMBER(6)
, first_name VARCHAR2(20)
, last_name VARCHAR2(25)
CONSTRAINT emp_last_name_nn_demo NOT NULL
, email VARCHAR2(25)
CONSTRAINT emp_email_nn_demo NOT NULL
, phone_number VARCHAR2(20)
, hire_date DATE DEFAULT SYSDATE
CONSTRAINT emp_hire_date_nn_demo NOT NULL
, job_id VARCHAR2(10)
CONSTRAINT emp_job_nn_demo NOT NULL
, salary NUMBER(8,2)
CONSTRAINT emp_salary_nn_demo NOT NULL
, commission_pct NUMBER(2,2)
, manager_id NUMBER(6)
, department_id NUMBER(4)
, dn VARCHAR2(300)
, CONSTRAINT emp_salary_min_demo
CHECK (salary > 0)
tablespace my_tbs_lt;
=======================================
I changed the initSID.ora file to have
Rollback_segments=( rbgui1t2, rbgui2t2, rbgui3t2, rbgui4t2)
=======================================
restarted everything
========================================
did a backup of the tablespace my_tbs_lt;
========================================
added some data to the table in the tablespace
========================================
ran a restore/recover - Get the error
========================================
It makes sense that I get the error because it is the tablespace that I have been working with, adding data. Is my logic correct? How does one restore a tablespace if it has rollback segments active? Can someone look to make sure I am declaring the rollback segments appropriately?

Thank you for the link - very helpful.
So would a more appropriate scheme be:
Create a tablespace
Create rollback segments
Put them online
enter their names in the ROLLBACK_SEGMENTS= segment(s)
I havent read everything, so you may say go look at the link again, but a second question. If you are managing the extent locally, does it not use a rollback segments, or is it using system, or is it actually creating rollback segments for itself within the context of the local management?
In my above scenario, I would have to take my rollback segment offline as well as the tablespace.

Wrong incarnation of this file - wrong creation SCN

We currently have a media recovery problem, and the problem seems not to get resolved.
System is Solaris 10 on a 64bits Sparc with 10.2.4 Oracle database.
Problem:
Can't recover from backup and archivelog fiiles.
We ran "alter database recover" and we got database altered and we open the database. But when query datafile table, the datafile (datafile 14) was still in recovered mode - I don't know how that happed.
Next, drop tablespace, inlucuding contents and added a new tablespace and the database opened again without error. But this time we still need the data from the old datafile.
We tried to add the old datafile to the tablespace, then we got "Wrong incarnation of this file - wrong creation SCN".
Where do we go from here?

Hemant K Chitale wrote:
drop tablespace, inlucuding contents and added a new tablespace That was absolutely the wrong thing to do.
Did you check to see if that datafile had been OFFLINE ? You could have attempted a RECOVER DATAFILE n and then ALTER DATABASE DATAFILE n ONLINE;Yes the datafile was offline
Given the situation you are in, you cannot add that tablespace back into the database.
So where do we start from here?
Your problem statement and the line "We ran "alter database recover"" aren't clear enough. Did you restore the database ? Or did you restore only a datafile ? OR did you not have to restore anything but just did a RECOVER DATABASE ?
This database does not have RMAN backup, ( the backup system is copy datafile to another folder) but we did a recover and the database recovered - as I said, we got "database alter" after we ran the recover command.
>
(if you can restore the database again and re-attempt recovery / online of that datafile, that would be one path to take --- but before you do so, please take another full {preferably COLD} backup of the database as it currently is !)
Yes, we back it up lastnight.

DB LINK Problem in Designer 2000 ver 2.0

Hi,
Description:
I have re-engineered a database into designer. The database name say is TEST. I have created another database called say TEST2 in TEST2 I have created a snapshot definition from one of the tables re-engineered from TEST.
Problem:
As soon as I try to generate the snapshot down to table level I can't see the db link to the remote database TEST in the DDL statement that was generated. I tried looking for a place in the database design but can't find a place to specifically define a database link.
In the database design I have specified that a db link extist but
there is no plcae to define the links name.
Code Exp:
PROMPT Creating Snapshot 'S_TABLE_OPPORTUNITY'
CREATE SNAPSHOT S_TABLE_OPPORTUNITY
STORAGE
INITIAL 310K
NEXT 310K
TABLESPACE TEST_GENERAL_DATA
REFRESH FORCE
WITH ROWID
AS
SELECT
NULL OBJID
FROM TABLE_OPPORTUNITY????looking for db link here
Please assist.

Hello
When you Use DAtabase Desing Transformer, check the options for generating the columns, its Key and related entities are chosen. U can find it in more options or any other button. then start genetaion
u should get the tables.
If still u are facing problem, delete the already generated table from DESIGN EDITOR.
regds
sai
null

TRANSACTION을 ROLLBACK SEGMENT에 할당하는 방법(SET TRANSACTION USE)

제품 : ORACLE SERVER
작성날짜 : 2003-04-04
TRANSACTION을 ROLLBACK SEGMENT에 할당하는 방법
==============================================
(SET TRANSACTION USE ROLLBACK SEGMENT)
Purpose
Batch job 등을 사용할 때 특별히 크게 만든 rollback segment를 사용하도록
할 수가 있다. transaction에 특정한 rbs를 지정하는 방법을 알아보자.
Explanation
Oracle은 다음과 같은 규칙에 의해 각 Transaction이 사용하는 Rollback
segment를 결정한다.
1. Active Transaction의 수가 가장 작은 Rollback Segment에 할당한다.
2. 만약 1의 조건에 만족하는 Rollback segment가 하나 이상이면, 가장
마지막에 할당된 rbs 다음의 rbs를 할당한다. 이것은 undo 기능을 더
오래 지속시키도록 해 준다.
그러나, Application이 큰 rollback segment가 필요하다면 위와 같이
자동적인 rollback segment의 할당이 아닌 Manual하게 특정 rollback
segment를 할당 가능하다.
다음의 방법을 사용한다.
1) 큰 rollback segment를 만든다. 큰 rollback segment 를 만들기
위해서는 rbs tablespace에 영역이 충분히 커야 하므로 필요할 경우
tablespace를 확장하는 작업을 한다.
<tablespace 확장>
$ sqlplus system/manager
sql> alter tablespace rbs add datafile '?/rbs1SID.dbf' size 100m;
<rollback segment 생성>
sql> create rollback segment big_rbs storage(initial 10m next 10m)
tablespace rbs;
sql> alter rollback segment big_rbs online;
2) Transaction 를 assign 한다.
<sqlplus>
SQL> set transaction use rollback segment big_rbs;
<pro*c>
exec sql commit work;
exec sql set transaction use rollback segment big_rbs;
<forms>
dbms_transaction.use_rollback_segment('big_rbs');
이와 같이 지정하면 이후에 commit 또는 rollback이 일어날 때까지
한 transaction에만 해당된다.

Can we addnew partition and sub partition in the existing table in one shor

can we addnew partition and sub partition in the existing table in one short

nav wrote:
can we addnew partition and sub partition in the existing table in one shortYes,
You can and below is the example for Range-List partition
ALTER TABLE <table_name>
   ADD PARTITION <partition_name> VALUES LESS THAN (<value>
      STORAGE (INITIAL 20K NEXT 20K) TABLESPACE <TS name> NOLOGGING
          SUBPARTITION Clause
          SUBPARTITION Clause
          SUBPARTITION Clause
          SUBPARTITION Clause
           );

Renaming VARRAY LOB

hello,
We am facing an issue using while renaming a table name. The issue is when I rename a table, it leaves external LOB table name unchanged.
For example, I create the table using the following. And when I try to rename TABLE_ALLWAVE to TEST_NEW_ALLWAVE, VOLTS_TEST, external LOB table doesnt change. Is there a way I can rename external VARRAY LOB table? Any help will really be appreciated.
CREATE TABLE TEST_allwave (
PROBEPOINT VARCHAR2(32),
NETNAME VARCHAR2(32),
MECH VARCHAR2(32),
UDATE DATE,
SAMPLES NUMBER(6),
PERIOD NUMBER(15,13),
FILE_NAME VARCHAR2(32),
TAIL VARCHAR2(32),
TRIGMECH VARCHAR2(32),
VOLTS asi_varray,
ANNOTATION CLOB default EMPTY_CLOB(),
INSERT_DT DATE)
VARRAY VOLTS STORE AS LOB VOLTS_TEST
storage (initial 1m next 1m)
tablespace abc_data;

Are you using the table created by Schema Registration ? Are you sure you had the correct namespace defined for the xdb prefix.. Can you run the following query
select table_name, parent_table_column, parent_table_name
from user_nested_tables

Space management issue

Hi,
Our one of the TS is having three datafiles, two of them having size of 1000 mb and one 512 mb.
File 1) 1000 mb ---- 74 % used
File 2) 1000 mb ---- 74 % used
File 3) 512 mb ---- 80 % used
Now, i have dropped the user and again imported the same through exp / imp.
After doing that one of the file 3) got empty and File 1) got full, File 2) 88 % used
Why the file 3) got empty ???
does the extents have been released ???
also the fragmentation in the TS got removed ??? will this improve the performance at some level ???
With Regards

Good to see you researching the topic, even if we are both now trading documents four and five years old!
There was actually a reason I wrote "Stating things generally..." in my first post: autoallocate is a complicated beast and a lot of subtleties arise when its in use that could take all day to discuss. Try this one, for example:
SQL> create table LMTA2 (col1 char(5)) storage (initial 16M next 16M) tablespace LMTA;
Table created.
SQL> select file_id from dba_extents where segment_name='LMTA2';
   FILE_ID
      7
      6
      7
      6
      7
      6
      7
      6
      7
      6
      7
      6
      7
      6
      7
      6
16 rows selected.That's round-robin in auto-allocated LMTs from extent 1 onwards, not extent 16 as stated in Tom's piece. Why? Because when you specify a large initial extent size when creating a table in autoallocated LMTs, Oracle skips allocating small 16K and 64K extents and goes straight to 1MB ones (or even 8MB or 64MB if the initial setting is large enough) -at which point the round robin technique kicks in from the get-go. It was a detail that I didn't bother to mention because it wasn't relevant to the point being made, I thought, though I will cheerfully confess to (and apologise for) having completely forgotten about round-robin kicking in after 1MB for small extent allocations. Your reminder from Tom's work is therefore a useful reminder for me.
Of course, re-looking at the OP's first post, I also see that he had 740MB of data in each of two datafiles, and he re-created his table via export/import. That amount of data means that the discussion about "less than 1MB of data in small extents doesn't round robin" is utterly irrelevant to the OP. Much more likely as an explanation, therefore, is that his export was done with COMPRESSION=Y, so that the import tried to create a single extent on re-import. Create a table in two-file autoallocate tablespace with INITIAL=1480M and you will (or might!) find the following extent distribution:
   FILE_ID BYTES/1024/1024
      7          64
      6          64
      7          64
      6          64
      7          64
      6          64
      7          64
      6          64
      7          64
      6          64
      7          64
      6          64
      7          64
      6          64
      7          64
      6          64
      7          64
      6          64
      6          64
      6          64
      6          64
      6          64
      6          64
      7           8Autoallocate has switched straight to 64MB extents, so we're immediately into round-robin and file 6 is mostly full (896MB) with the residual coming from file 7 (576MB plus an extra 8MB). So that more or less explains why the OP's file 1 is full (or nearly so) and file 2 is not.
But an even more interesting point arises: that listing of extents is in extent ID order and therefore represents the order in which they were allocated by the database. That chunk of six repeated allocations to file 6 after a bit of round-robin (extents 18 to 23) is another example of why I spoke "in general terms" the first time I posted: this thing is not straightforward and even when you think you're into round robin mode, Oracle can switch out of that when it feels it appropriate to do so! There's a reason why this thing is "automatic", after all!
Nevertheless, if it proves impossible to describe every last nuance of autoallocate behaviour in a short post, it is possible to say, clearly, that writing that "Oracle's correct behaviour is to allocate extents in a Round Robin fashion" is extremely untrue. The behaviour is a lot more subtle and complex than that.

When tablespace next extend happen

9i/10g AIX/Sun
when tablespace next extend happen?
what thresshold is another extent acquired, or does it just get another when it runs out of space?

According to the
Oracle® Database Concepts
10g Release 2 (10.2)
Part Number B14220-02
"When you create a table, Oracle allocates to the table's data segment an initial
extent of a specified number of data blocks. Although no rows have been inserted
yet, the Oracle data blocks that correspond to the initial extent are reserved for
that table's rows.
If the data blocks of a segment's initial extent become full and more space is
required to hold new data, Oracle automatically allocates an incremental extent
for that segment. An incremental extent is a subsequent extent of the same or
greater size than the previously allocated extent in that segment."
Sim

How will include next cluase to our present tablespace

Hi,
I have add datafile to our tablespace , but by mistak i have not include NEXT clause
how will include next clause.
i have use following command
alter database datafile '/oradata/ocr1.dbf' next 100M;
alter database datafile '/oradata/ocr1.dbf' next 100M
ERROR at line 1:
ORA-01916: keyword ONLINE, OFFLINE, RESIZE, AUTOEXTEND or END/DROP expected

I will got the answer
alter database datafile '/oradata/ocr1.dbf' autoextend on next 100M;

Probleme insertion dans default tablespace

Qui peut m'expliquer pourquoi quand je fais une insertion dans
une table qui a par difault un tablespace, les donnies vont dans tablespace systeme.

Je ne comprends pas ce que tu entends par:
"une table qui a par difault un tablespace"
Quel syntax as-tu utilisi pour crier cette table?
A la fin du create table tu peux difinir le tablespace (voir example ci-dessous):
CREATE TABLE salgrade
( grade NUMBER CONSTRAINT pk_salgrade
PRIMARY KEY
USING INDEX TABLESPACE users_a,
losal NUMBER,
hisal NUMBER )
TABLESPACE human_resource
STORAGE (INITIAL 6144
NEXT 6144
MINEXTENTS 1
MAXEXTENTS 5 );

Goldengate 11.1.1.1 Oracle 11.2 Encrypted tablespace

Please advise why this error is showing and help us on this situation
Line: -----
Windows 2008 x64
Oracle 11.2.0.1 x64
Oracle Goldengate 11.1.1.1 x64
++++++++++++SOURCE++++++++++++++
sql>conn / as sysdba
**************CREATE TABLESPACE AND TABLE********************
CREATE TABLESPACE encrypted_ts
DATAFILE 'd:\oradata\test\encrypted_ts01.dbf' SIZE 128K
SIZE 15M
AUTOEXTEND ON NEXT 20M
MAXSIZE UNLIMITED
LOGGING
ENCRYPTION USING 'AES192'
EXTENT MANAGEMENT LOCAL
SEGMENT SPACE MANAGEMENT AUTO
DEFAULT NOCOMPRESS STORAGE(ENCRYPT);
CREATE TABLE TESTA
ID NUMBER,
NAME VARCHAR2(16 CHAR)
LOGGING
NOCOMPRESS
NOCACHE
NOPARALLEL
MONITORING;
cmd> mkstore -wrl d:\test\wallet -createEntry ORACLE.SECURITY.CL.ENCRYPTION.ORACLEGG
Enter <secret> : test
cmd>mkstore -wrl d:\test\wallet -viewEntry ORACLE.SECURITY.CL.ENCRYPTION.ORACLEGG
ORACLE.SECURITY.CL.ENCRYPTION.ORACLEGG = test
sql>ALTER SYSTEM SET ENCRYPTION WALLET CLOSE IDENTIFIED BY 'welcome1';
sql>ALTER SYSTEM SET ENCRYPTION WALLET OPEN IDENTIFIED BY 'welcome1';
Compile dbms_internal_clkm package.
sql>@prvtclkm.plb
sql>GRANT EXECUTE ON SYS.DBMS_INTERNAL_CLKM TO GGS_OWNER;
**********************************GOLDENGATE******************************************
ggsci>dblogin userid ggs_owner, ggs_owner
ggsci>add extract ext2ts, tranlog, begin now
ggsci>add rmttrail D:\ggs\dirdat\ts, extract ext2ts
ggsci>ENCRYPT PASSWORD test ENCRYPTKEY DEFAULT
Using default key...
Encrypted password: AACAAAAAAAAAAAEAZAMEFCPGPEOHYDHE
ggsci>edit params ext2ts
EXTRACT ext2ts
USERID ggs_owner, PASSWORD ggs_owner
RMTHOST 192.168.0.2, MGRPORT 7809
RMTTRAIL D:\ggs\dirdat\ts
DBOPTIONS DECRYPTPASSWORD AACAAAAAAAAAAAEAZAMEFCPGPEOHYDHE ENCRYPTKEY DEFAULT -- ???
TABLE TESTA;
+++++++++++++TARGET++++++++++++++++
sql> conn / as sysdba
**************CREATE TABLESPACE AND TABLE********************
cmd>
CREATE TABLESPACE ts
LOGGING DATAFILE 'd:\oradata\test\ts.dbf'
SIZE 15M
AUTOEXTEND ON NEXT 20M
EXTENT MANAGEMENT
LOCAL SEGMENT SPACE
MANAGEMENT AUTO;
CREATE TABLE TESTA
ID NUMBER,
NAME VARCHAR2(16 CHAR)
LOGGING
NOCOMPRESS
NOCACHE
NOPARALLEL
MONITORING;
************************************GOLDENGATE*****************************************
ggsci>DBLOGIN USERID ggs_owner, PASSWORD ggs_owner
ggsci>ADD CHECKPOINTTABLE GGS_OWNER.CHKPTAB
ggsci>ADD REPLICAT rep1, EXTTRAIL D:\ggs\dirdat\ts, CHECKPOINTTABLE GGS_OWNER.CHKPTAB
ggsci>EDIT PARAMS rep1
REPLICAT rep1
ASSUMETARGETDEFS
USERID ggs_owner, PASSWORD ggs_owner
MAP GGS_OWNER.TESTA, TARGET GGS_OWNER.TESTA;
+++++++++++++TARGET+++++++++++++++
ggsci>start replicat rep1
+++++++++++++SOURCE+++++++++++++++
ggsci>start extract ext2ts
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!EXTRACT - REPORT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
2011-07-05 11:46:50 ERROR OGG-01028 ORA-06521: PL/SQL: Error mapping function
ORA-06512: at "SYS.DBMS_INTERNAL_CLKM", line 3
ORA-06512: at line 1.
2011-07-05 11:46:50 ERROR OGG-01668 PROCESS ABENDING.
Edited by: Oyunbold on Jul 7, 2011 3:25 AM
Edited by: Oyunbold on Jul 19, 2011 6:09 PM

Yesterday, I met the same problem. How do you solve it ? Plz, help me.
OS : AIX 5.3
DB : Oracle 11.1.0.7
OGG : 11.1.1.1
2011-09-06 15:26:56 INFO OGG-01515 Oracle GoldenGate Capture for Oracle, eora01.prm: Positioning to begin time Sep 2, 2011 6:50:49 PM.
2011-09-06 15:26:56 ERROR OGG-01028 Oracle GoldenGate Capture for Oracle, eora01.prm: ORA-12427: invalid input value for FLAGS parameter ORA-06512: at "SYS.DBMS_INTERNAL_CLKM", line 3 ORA-06512: at line 1.
2011-09-06 15:26:56 ERROR OGG-01668 Oracle GoldenGate Capture for Oracle, eora01.prm: PROCESS ABENDING.
Our Extract configuration is below :
EXTRACT EORA01
USERID ogg, PASSWORD AACAAAAAAAAAAADAHBMDHBECUCZBPIYE, encryptkey XKEY
DBOPTIONS DECRYPTPASSWORD AACAAAAAAAAAAAIARIXFKCQBMFIGFARA ENCRYPTKEY DEFAULT
ENCRYPTTRAIL
exttrail ./dirdat/ea
EOFDELAYCSECS 50
FLUSHCSECS 50
DISCARDFILE ./dirrpt/EORA01.DSC, APPEND, MEGABYTES 500
DISCARDROLLOVER AT 07:30
TABLE TVANBT.TLF_BUYS_MISS;
...

Next Entend (Tablespace)

Similar Messages

Maybe you are looking for