Re: Issue while copying Serialized object tables (F989998, F989999) (max

Re: Issue while copying Serialized object tables (F989998, F989999) (max

Hi,

Why don't you make a simply import. The only detail you have to remember is
to grant privilege to *public after the import procedure.

Related the error you are receiving. Have you really checked that the table
is recreate or it just delete records?




antoine_mpo
<[email protected] To: [email protected]
> cc:
Sent by: Subject: Issue while copying Serialized object tables (F989998, F989999) (max extents
jdelist-bounces@j reached)
delist.com


12/07/2004 15:09
Please respond to
"PeopleSoft®
EnterpriseOne"






Hi List,

I'm working on a way to make full generation during the day, while people
are working.
I created a set of F989998 and F989999 tables in another data source, and
an ocm mapping for a particular user to use those tables.
I can then make my full html generation.

But my problem is when i want to copy those tables to the "real" tables
used by end-users.
When i'm trying to copy them by JDE copy process, i get the following
Oracle Error : "ORA-01631: max # extents (505) reached in table
DV7333.F989999"
It's because in JDE copy process, JDE first drop the table, then re-create
it, so it's no use to change the maxextents parameter on the table ! And i
don't know where is took that parameter of 505 max extents !
Any idea ?

For the moment i'm using R98403 report, in "append" mode to work around the
issue, but it's taking too much time !

The other solution would be to export/import the table, but i found! it a
pain in the ass.

Any idea would be appreciated.
How do you do yourself ?

Thansk for your help.

Cheers,


Antoine. OW system Administrator OneWorld Xe, Update 6, SP20 One-Off R1
Windows Servers (NT and 2000) Oracle 8i Databases Websphere 4 on JAS
servers



The entire JDELIST thread is available for viewing.



This is the JDELIST Applications Mailing List.
The instructions on how to unsubscribe from any JDELIST mailing
list are available here.
JDELIST is not affiliated with JDEdwards®.









The information transmitted is intended only for the person(s)or entity
to which it is addressed and may contain confidential and/or legally
privileged material. Delivery of this message to any person other than
the intended recipient(s) is not intended in any way to waive privilege
or confidentiality. Any review, retransmission, dissemination or other
use of, or taking of any action in reliance upon, this information by
entities other than the intended recipient is prohibited. If you
receive this in error, please contact the sender and delete the
material from any computer.

For Translation:

http://www.baxter.com/email_disclaimer

Re: Issue while copying Serialized object tables (F989998, F989999) (max

Hi,

In the export/import process, the thing i don't like is that it's always the mess for recreate the index in the write tablespace (not in the data tablespace).
But yes i could to that.

Concerning the extents issue, yes i'm sure that jde first drop the table and re-create it before copying the records.
I checked the logs.

Cheers,

Re: Issue while copying Serialized object tables (F989998, F989999) (max

Hi,

Why do not try to create the table yourself through Oracle with the extend
parameter to 1. If it works, it could mean that you have get the max
extends limit in you tablespace.

Regards




antoine_mpo
<[email protected] To: [email protected]
> cc:
Sent by: Subject: Re: Issue while copying Serialized object tables (F989998, F989999) (max
jdelist-bounces@j extents reached)
delist.com


13/07/2004 12:45
Please respond to
"PeopleSoftï½®
EnterpriseOne"






Hi,

I did a try, but unfortunately, this batch is working the same way as JDE
table copy : first it drop the table in the target data source, then
recreate it and then make the copy.

So i will probably have the same problem of max extents while copying the
serialized objects tables.

Thanks,

Cheers,


Antoine. OW system Administrator OneWorld Xe, Update 6, SP20 One-Off R1
Windows Servers (NT and 2000) Oracle 8i Databases Websphere 4 on JAS
servers



The entire JDELIST thread is available for viewing.



This is the JDELIST Applications Mailing List.
The instructions on how to unsubscribe from any JDELIST mailing
list are available here.
JDELIST is not affiliated with JDEdwards®.






The information transmitted is intended only for the person(s)or entity
to which it is addressed and may contain confidential and/or legally
privileged material. Delivery of this message to any person other than
the intended recipient(s) is not intended in any way to waive privilege
or confidentiality. Any review, retransmission, dissemination or other
use of , or taking of any action in reliance upon, this information by
entities other than the intended recipient is prohibited. If you
receive this in error, please contact the sender and delete the
material from any computer.

For Translation:

http://www.baxter.com/email_disclaimer

Re: Issue while copying Serialized object tables (F989998, F989999) (max

It seams that you are using Oracle database. This is how storage parameters works in Oracle. If the storage parameters are not specified at Object level then it takes the default storage parameter at the tablespace level. Change the default storage parameter at the tablespace level and it may help ( Provided these parameters are not passed with table creation.

Re: Issue while copying Serialized object tables (F989998, F989999) (max

Hi Vivek,

Yes i knew that when you create a table, if the maxextents is not precised in the sql request, it takes the default value of the tablespace, but i didn't remember where to find this default value.
It was because i was using Toad to search in the Tablespace, and couldn't find where it was. But i used DBA Studio and find the Default Storage parameters of my tablespace, where maxextents was set to 505 instead of unlimited.

So now i can try to use JDE copy now.

Thanks for all your answers folks !