[Date Prev][Date Next][Thread Prev][Thread Next]
[Author Index]
[Date Index]
[Thread Index]
[SQR-USERS Info]
[SQRUG Home Page]
Re: PeopleSoft SQR Problem BEN733
- Subject: Re: PeopleSoft SQR Problem BEN733
- From: "Campbell, Andrew" <acampbell@UNITEDMEDIA.COM>
- Date: Thu, 10 Sep 1998 16:05:13 -0400
Also check your indexes..It might be doing a table scan...and running
out of temp space..
> -----Original Message-----
> From: Brian Karlisch [SMTP:brian.karlisch@BNE.NET]
> Sent: Thursday, September 10, 1998 3:56 PM
> To: Multiple recipients of list SQR-USERS
> Subject: Re: PeopleSoft SQR Problem BEN733
>
> You will need to get your DBA to increase the tablespace PSTEMP. They
> will
> use the ALTER TABLESPACE ADD DATAFILE command.
>
>
> -----Original Message-----
> From: Discussion of SQR, SQRIBE Technologies's database
> reporting language [mailto:SQR-USERS@list.iex.net] On Behalf Of Greg
> Gargett
> Sent: Thursday, September 10, 1998 2:51 PM
> To: Multiple recipients of list SQR-USERS
> Subject: Re: PeopleSoft SQR Problem BEN733
>
> try defragging your database.
>
> Bill Bowers wrote:
>
> > We are unable to run our PeopleSoft delivered SQR, BEN733 the
> Base
> > Benefits Audit, in our environment: Payroll, HR and Ben Admin.
> It
> > always stops at the same routine: Employee and Spouse (or
> other
> > Dependent) Both Electing Health Benefit. The routine purpose
> and
> > header are printed and nothing else.
> >
> > The error we get is:
> >
> > (SQR 5528) ORACLE OFETCH error - 1652 in cursor 6:
> > ORA-01652: unable to extend temp seqment by 8 in tablespace
> PSTEMP
> >
> > Error on line 322:
> > (SQR 3725) Bad return fetching row from database.
> >
> > SQRW: Program Aborting.
> >
> > We have tried the following without success:
> > 1. Increasing the size of the temporary tablespace (PSTEMP) to
> 1GB.
> > 2. Making PSTEMP permanent in order for Oracle's SMON process
> to
> > clean it up.
> > 3. The required tables do in fact exist.
> > 4. Ensuring that the unique indexes are in place for all the
> affected
> > tables.
> > 5. Allocated sufficient size for batch rollback segments.
> >
> > Does anybody have any ideas on how this problem may be
> corrected?
> >
> > Bill