SGA_MAX_SIZE limitations in Oracle 9i

Hello everyone,
I did oracle 9.2.0.4 installation on RHEL4 and created one database.
I was editing init parameters depending upon our database requirements.
while setting parameter SGA_MAX_SIZE=2.5GB i got an error regarding "Shared Memory Segment" and i not able to set my SGA_MAX_SIZE more than 1.5GB.
I am pretty sure this error is due to kernel parameter shmmax.
And as per oracle recommendations we can set kernel.shmmax to 4GB at max.. So we set our shmmax to 4GB.. but this is not allowing me to set my sga_max_size more than 1.5G
Any recommendations, suggestions would be greatly appreciated.
Thanks

sumit patil wrote:
Hello Aman , plz can u send me d exact syllabus of 1z0-042 (10g Admin1) paper. Plz help me , m in real need.
Thank U..
My email ID is [email protected]
Edited by: sumit patil on Jul 4, 2009 9:08 AMTwo things,
1) What 042 and its syllabus has to do AT ALL with this thread whatsoever? You shoudl know that if you are hijacking a thread like this, it doesn't show very good attitude.
2) Its a bad idea to post your email on a public forum.
That said, all the papers and their contents are very well documented over http://education.oracle.com . As you have asked a wrong question at a wrong thread, so I would leave it for you to search your paper from ther.
HTH
Aman....

Similar Messages

2GB OR NOT 2GB - FILE LIMITS IN ORACLE

제품 : ORACLE SERVER
작성날짜 : 2002-04-11
2GB OR NOT 2GB - FILE LIMITS IN ORACLE
======================================
Introduction
~~~~~~~~~~~~
This article describes "2Gb" issues. It gives information on why 2Gb
is a magical number and outlines the issues you need to know about if
you are considering using Oracle with files larger than 2Gb in size.
It also
looks at some other file related limits and issues.
The article has a Unix bias as this is where most of the 2Gb issues
arise but there is information relevant to other (non-unix)
platforms.
Articles giving port specific limits are listed in the last section.
Topics covered include:
Why is 2Gb a Special Number ?
Why use 2Gb+ Datafiles ?
Export and 2Gb
SQL*Loader and 2Gb
Oracle and other 2Gb issues
Port Specific Information on "Large Files"
Why is 2Gb a Special Number ?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Many CPU's and system call interfaces (API's) in use today use a word
size of 32 bits. This word size imposes limits on many operations.
In many cases the standard API's for file operations use a 32-bit signed
word to represent both file size and current position within a file (byte
displacement). A 'signed' 32bit word uses the top most bit as a sign
indicator leaving only 31 bits to represent the actual value (positive or
negative). In hexadecimal the largest positive number that can be
represented in in 31 bits is 0x7FFFFFFF , which is +2147483647 decimal.
This is ONE less than 2Gb.
Files of 2Gb or more are generally known as 'large files'. As one might
expect problems can start to surface once you try to use the number
2147483648 or higher in a 32bit environment. To overcome this problem
recent versions of operating systems have defined new system calls which
typically use 64-bit addressing for file sizes and offsets. Recent Oracle
releases make use of these new interfaces but there are a number of issues
one should be aware of before deciding to use 'large files'.
What does this mean when using Oracle ?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
The 32bit issue affects Oracle in a number of ways. In order to use large
files you need to have:
1. An operating system that supports 2Gb+ files or raw devices
2. An operating system which has an API to support I/O on 2Gb+ files
3. A version of Oracle which uses this API
Today most platforms support large files and have 64bit APIs for such
files.
Releases of Oracle from 7.3 onwards usually make use of these 64bit APIs
but the situation is very dependent on platform, operating system version
and the Oracle version. In some cases 'large file' support is present by
default, while in other cases a special patch may be required.
At the time of writing there are some tools within Oracle which have not
been updated to use the new API's, most notably tools like EXPORT and
SQL*LOADER, but again the exact situation is platform and version specific.
Why use 2Gb+ Datafiles ?
~~~~~~~~~~~~~~~~~~~~~~~~
In this section we will try to summarise the advantages and disadvantages
of using "large" files / devices for Oracle datafiles:
Advantages of files larger than 2Gb:
On most platforms Oracle7 supports up to 1022 datafiles.
With files < 2Gb this limits the database size to less than 2044Gb.
This is not an issue with Oracle8 which supports many more files.
In reality the maximum database size would be less than 2044Gb due
to maintaining separate data in separate tablespaces. Some of these
may be much less than 2Gb in size.
Less files to manage for smaller databases.
Less file handle resources required
Disadvantages of files larger than 2Gb:
The unit of recovery is larger. A 2Gb file may take between 15 minutes
and 1 hour to backup / restore depending on the backup media and
disk speeds. An 8Gb file may take 4 times as long.
Parallelism of backup / recovery operations may be impacted.
There may be platform specific limitations - Eg: Asynchronous IO
operations may be serialised above the 2Gb mark.
As handling of files above 2Gb may need patches, special configuration
etc.. there is an increased risk involved as opposed to smaller files.
Eg: On certain AIX releases Asynchronous IO serialises above 2Gb.
Important points if using files >= 2Gb
Check with the OS Vendor to determine if large files are supported
and how to configure for them.
Check with the OS Vendor what the maximum file size actually is.
Check with Oracle support if any patches or limitations apply
on your platform , OS version and Oracle version.
Remember to check again if you are considering upgrading either
Oracle or the OS in case any patches are required in the release
you are moving to.
Make sure any operating system limits are set correctly to allow
access to large files for all users.
Make sure any backup scripts can also cope with large files.
Note that there is still a limit to the maximum file size you
can use for datafiles above 2Gb in size. The exact limit depends
on the DB_BLOCK_SIZE of the database and the platform. On most
platforms (Unix, NT, VMS) the limit on file size is around
4194302*DB_BLOCK_SIZE.
Important notes generally
Be careful when allowing files to automatically resize. It is
sensible to always limit the MAXSIZE for AUTOEXTEND files to less
than 2Gb if not using 'large files', and to a sensible limit
otherwise. Note that due to <Bug:568232> it is possible to specify
an value of MAXSIZE larger than Oracle can cope with which may
result in internal errors after the resize occurs. (Errors
typically include ORA-600 [3292])
On many platforms Oracle datafiles have an additional header
block at the start of the file so creating a file of 2Gb actually
requires slightly more than 2Gb of disk space. On Unix platforms
the additional header for datafiles is usually DB_BLOCK_SIZE bytes
but may be larger when creating datafiles on raw devices.
2Gb related Oracle Errors:
These are a few of the errors which may occur when a 2Gb limit
is present. They are not in any particular order.
ORA-01119 Error in creating datafile xxxx
ORA-27044 unable to write header block of file
SVR4 Error: 22: Invalid argument
ORA-19502 write error on file 'filename', blockno x (blocksize=nn)
ORA-27070 skgfdisp: async read/write failed
ORA-02237 invalid file size
KCF:write/open error dba=xxxxxx block=xxxx online=xxxx file=xxxxxxxx
file limit exceed.
Unix error 27, EFBIG
Export and 2Gb
~~~~~~~~~~~~~~
2Gb Export File Size
~~~~~~~~~~~~~~~~~~~~
At the time of writing most versions of export use the default file
open API when creating an export file. This means that on many platforms
it is impossible to export a file of 2Gb or larger to a file system file.
There are several options available to overcome 2Gb file limits with
export such as:
- It is generally possible to write an export > 2Gb to a raw device.
Obviously the raw device has to be large enough to fit the entire
export into it.
- By exporting to a named pipe (on Unix) one can compress, zip or
split up the output.
See: "Quick Reference to Exporting >2Gb on Unix" <Note:30528.1>
- One can export to tape (on most platforms)
See "Exporting to tape on Unix systems" <Note:30428.1>
(This article also describes in detail how to export to
a unix pipe, remote shell etc..)
Other 2Gb Export Issues
~~~~~~~~~~~~~~~~~~~~~~~
Oracle has a maximum extent size of 2Gb. Unfortunately there is a problem
with EXPORT on many releases of Oracle such that if you export a large table
and specify COMPRESS=Y then it is possible for the NEXT storage clause
of the statement in the EXPORT file to contain a size above 2Gb. This
will cause import to fail even if IGNORE=Y is specified at import time.
This issue is reported in <Bug:708790> and is alerted in <Note:62436.1>
An export will typically report errors like this when it hits a 2Gb
limit:
. . exporting table BIGEXPORT
EXP-00015: error on row 10660 of table BIGEXPORT,
column MYCOL, datatype 96
EXP-00002: error in writing to export file
EXP-00002: error in writing to export file
EXP-00000: Export terminated unsuccessfully
There is a secondary issue reported in <Bug:185855> which indicates that
a full database export generates a CREATE TABLESPACE command with the
file size specified in BYTES. If the filesize is above 2Gb this may
cause an ORA-2237 error when attempting to create the file on IMPORT.
This issue can be worked around be creating the tablespace prior to
importing by specifying the file size in 'M' instead of in bytes.
<Bug:490837> indicates a similar problem.
Export to Tape
~~~~~~~~~~~~~~
The VOLSIZE parameter for export is limited to values less that 4Gb.
On some platforms may be only 2Gb.
This is corrected in Oracle 8i. <Bug:490190> describes this problem.
SQL*Loader and 2Gb
~~~~~~~~~~~~~~~~~~
Typically SQL*Loader will error when it attempts to open an input
file larger than 2Gb with an error of the form:
SQL*Loader-500: Unable to open file (bigfile.dat)
SVR4 Error: 79: Value too large for defined data type
The examples in <Note:30528.1> can be modified to for use with SQL*Loader
for large input data files.
Oracle 8.0.6 provides large file support for discard and log files in
SQL*Loader but the maximum input data file size still varies between
platforms. See <Bug:948460> for details of the input file limit.
<Bug:749600> covers the maximum discard file size.
Oracle and other 2Gb issues
~~~~~~~~~~~~~~~~~~~~~~~~~~~
This sections lists miscellaneous 2Gb issues:
- From Oracle 8.0.5 onwards 64bit releases are available on most platforms.
An extract from the 8.0.5 README file introduces these - see <Note:62252.1>
- DBV (the database verification file program) may not be able to scan
datafiles larger than 2Gb reporting "DBV-100".
This is reported in <Bug:710888>
- "DATAFILE ... SIZE xxxxxx" clauses of SQL commands in Oracle must be
specified in 'M' or 'K' to create files larger than 2Gb otherwise the
error "ORA-02237: invalid file size" is reported. This is documented
in <Bug:185855>.
- Tablespace quotas cannot exceed 2Gb on releases before Oracle 7.3.4.
Eg: ALTER USER <username> QUOTA 2500M ON <tablespacename>
reports
ORA-2187: invalid quota specification.
This is documented in <Bug:425831>.
The workaround is to grant users UNLIMITED TABLESPACE privilege if they
need a quota above 2Gb.
- Tools which spool output may error if the spool file reaches 2Gb in size.
Eg: sqlplus spool output.
- Certain 'core' functions in Oracle tools do not support large files -
See <Bug:749600> which is fixed in Oracle 8.0.6 and 8.1.6.
Note that this fix is NOT in Oracle 8.1.5 nor in any patch set.
Even with this fix there may still be large file restrictions as not
all code uses these 'core' functions.
Note though that <Bug:749600> covers CORE functions - some areas of code
may still have problems.
Eg: CORE is not used for SQL*Loader input file I/O
- The UTL_FILE package uses the 'core' functions mentioned above and so is
limited by 2Gb restrictions Oracle releases which do not contain this fix.
<Package:UTL_FILE> is a PL/SQL package which allows file IO from within
PL/SQL.
Port Specific Information on "Large Files"
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Below are references to information on large file support for specific
platforms. Although every effort is made to keep the information in
these articles up-to-date it is still advisable to carefully test any
operation which reads or writes from / to large files:
Platform See
~~~~~~~~ ~~~
AIX (RS6000 / SP) <Note:60888.1>
HP <Note:62407.1>
Digital Unix <Note:62426.1>
Sequent PTX <Note:62415.1>
Sun Solaris <Note:62409.1>
Windows NT Maximum 4Gb files on FAT
Theoretical 16Tb on NTFS
** See <Note:67421.1> before using large files
on NT with Oracle8
*2 There is a problem with DBVERIFY on 8.1.6
See <Bug:1372172>

I'm not aware of a packaged PL/SQL solution for this in Oracle 8.1.7.3 - however it is very easy to create such a program...
Step 1
Write a simple Java program like the one listed:
import java.io.File;
public class fileCheckUtl {
public static int fileExists(String FileName) {
File x = new File(FileName);
if (x.exists())
return 1;
else return 0;
public static void main (String args[]) {
fileCheckUtl f = new fileCheckUtl();
int i;
i = f.fileExists(args[0]);
System.out.println(i);
Step 2 Load this into the Oracle data using LoadJava
loadjava -verbose -resolve -user user/pw@db fileCheckUtl.java
The output should be something like this:
creating : source fileCheckUtl
loading : source fileCheckUtl
creating : fileCheckUtl
resolving: source fileCheckUtl
Step 3 - Create a PL/SQL wrapper for the Java Class:
CREATE OR REPLACE FUNCTION FILE_CHECK_UTL (file_name IN VARCHAR2) RETURN NUMBER AS
LANGUAGE JAVA
NAME 'fileCheckUtl.fileExists(java.lang.String) return int';
Step 4 Test it:
SQL> select file_check_utl('f:\myjava\fileCheckUtl.java') from dual
2 /
FILE_CHECK_UTL('F:\MYJAVA\FILECHECKUTL.JAVA')
1

Limitations of Oracle 10G XE as against Oracle 10G Standard Edition

Can you please give the information regarding....
1. Capabilities of Oracle 10G XE (Express Edition)
2. Limitations of Oracle 10G XE as against Oracle 10G Standard Edition

Have a look at the License Information:
http://download-uk.oracle.com/docs/cd/B25329_01/doc/license.102/b25456/toc.htm#BABJBGGA
There's also a feature matrix in pdf-format:
http://www.oracle.com/technology/products/database/oracle10g/pdf/twp_general_10gdb_product_family.pdf
C.
Message was edited by:
cd

Four GB of user data Limitation in Oracle 10g XE

Hi Mates!
There is one limitation in oracle XE which is:
It stores up to four GB of user data.
I am planning to migrate my database from Oracle 9i to Oracle 10g XE. My queries are below:
1. Is it possible to migrate from Oracle 9i to Oracle 10g XE?
2. I am confused regarding Four GB of user data Limitation. I don't understand nothing much about this. Presently If I prepare a dump (export) file in oracle 9i the size becomes around 250MB. If I switch to oracle 10g XE, how long will I be able to use my database?
Rgds,
Luther

Hi Mates!
There is one limitation in oracle XE which is:
It stores up to four GB of user data.
I am planning to migrate my database from Oracle 9i
to Oracle 10g XE. My queries are below:
1. Is it possible to migrate from Oracle 9i to Oracle
10g XE?this is a simple test case, you can install XE, export from 9i and import to XE. I did it before, it worked for me, but this does not mean it will for you, testing is only way to be sure.
There are lots of limitation of XE mentioned in the Licensing Information Guide.
http://www.oracle.com/pls/xe102/homepage?remark=tahiti
2. I am confused regarding Four GB of user data
Limitation. I don't understand nothing much about
this. Presently If I prepare a dump (export) file in
oracle 9i the size becomes around 250MB. If I switch
to oracle 10g XE, how long will I be able to use my
database?My XE is ~3,3 GB total, datafile + tempfile size, apex applications are working without problem. But consider all syatem + user data as a total, so 250 MB user data won't be a problem, most probably.
Rgds,
Luther

Project Variable limitation in Oracle 11G BPM

hi,
Is there any limitation with Oracle 11G BPM on the number of project variable that can be created for a given BPMN processs ??
example , instance is not getting created if the number of int Project variable is more than 10. If there are 10 INT project variable , instance getting created ...
Thanks

Hi,
Oracle doesn't provide the source code 11g Worklist. If you want to customize the existing worklistapp, then you can try modifying the jsfs in exploded directory, but that requires tedious knowledge in ADF.
I would recommend to write your custom worklist app. Oracle provides various taskflows available in JDeveloper, you can just include them in the application to make things work.

MATRIX LIMITATION IN ORACLE

Hi,
I encountered this problem in my matrix report implementation:
I have a matrix which has a column with fixed width. The row height was initially fixed but I had to change it so that the height is now variable. Problem is, I can't seem to make the column height for each row expand to follow the height of each row (which varies). The height for the columns seem to be fixed no matter what I do. see, I need the height to expand so that I can put a border around every cell which matches the height of the row and column. Is this really an oracle limitation? Thanks
by the way, if you're interested, here's how it looks like:
alkjf;ajfa;jfd |matrix|
adfafdafdadf --------
alkjf;ajfa;jfd |matrix|
adfafdafdadf --------
I want it to look like this:
alkjf;ajfa;jfd |matrix|
adfafdafdadf | |
________________|______|___
alkjf;ajfa;jfd |matrix|
adfafdafdadf | |
________________|______|___

It's a limitation in Oracle. Google for error message
ORA--01795
This link will give you a workaround:
http://www.dbforums.com/showthread.php?t=1004840&goto=nextoldest
Basically, you need to avoid sending IN lists that contain
more than 1,000 items. You can do this one of two ways...
WHERE blah IN (1, 2, ..., 1000) OR blah IN (1001, 1002, ....,
2000) ...
-or-
(SELECT * FROM mytable WHERE blah IN (1, 2, ..., 1000))
UNION
(SELECT * FROM mytable WHERE blah IN (1001, 1002, ..., 2000))
...

Limitations in Oracle XE with respect to SQL

Hi to all,
Is there are any limitations in SQL Queries in Oracle XE?
Because I am running a SQL query in Oracle Standard Edition which is returing results whereas I am not able to run the same query against the Oracle XE with the same table structure and same data.
In Oracle XE it is throwing the error as ERROR at line 31:
ORA-00904: "EMP"."EMPLOYEE_CODE": invalid identifier
My query is
SELECT "EMP"."EMPLOYEE_CODE",
"EMP"."NAME",
"EMP"."BIRTH_DATE",
"EMP"."FH_NAME",
"EMP"."JOINING_DATE",
"EMP"."DESIGNATION",
"EMP"."PAN_NO",
"DEPT"."DESCRIPTION",
"EMP"."DIVISION_CODE",
"DIV"."DESCRIPTION",
"LOC"."DESCRIPTION",
"EMP"."PF_NO",
"EMP"."ESI_NO",
"EMP"."CURRENT_STATUS",
"L"."CL_BALANCE",
"L"."EL_BALANCE",
"L"."ML_BALANCE" ,
"A"."ATTENDED_DAYS",
"A"."PUBLIC_HOLIDAYS",
"A"."WEEKLY_HOLIDAYS",
(SELECT SUM(CASE WHEN "LEAVE"."LEAVE_CODE"='CL' THEN "LEAVE"."LEAVE_DAYS" END ) CASUAL_LEAVE FROM LEAVE WHERE PERIOD=88 AND EMPLOYEE_CODE=EMP.EMPLOYEE_CODE) AS CASUAL_LEAVE,
(SELECT SUM(CASE WHEN "LEAVE"."LEAVE_CODE"='EL' THEN "LEAVE"."LEAVE_DAYS" END) EARNED_LEAVE FROM LEAVE WHERE PERIOD=88 AND EMPLOYEE_CODE=EMP.EMPLOYEE_CODE) AS EARNED_LEAVE,
"SICK_LEAVE",
"ON_DUTY",
"ESI_LEAVE",
(SELECT SUM(CASE WHEN "LEAVE"."LEAVE_CODE"='LP' THEN "LEAVE"."LEAVE_DAYS" END) LOSS_OF_PAY_DAYS FROM LEAVE WHERE PERIOD=88 AND EMPLOYEE_CODE=EMP.EMPLOYEE_CODE) AS LOSS_OF_PAY_DAYS,
"PAID_DAYS", "DIV"."ADDRESS2"||' '||"DIV"."ADDRESS3" AS ADDRESS,
(SELECT SUM(AMOUNT) FROM(
SELECT A.EMPLOYEE_CODE, SUM(A.AMOUNT) AS AMOUNT FROM PAYROLL A, PAY_ELEMENT B
WHERE A.PAY_ELEMENT_CODE=B.PAY_ELEMENT_CODE AND
A.PERIOD= 88 AND A.EMPLOYEE_CODE=EMP.EMPLOYEE_CODE AND B.PAY_ELEMENT_TYPE='E'
AND B.PAY_ELEMENT_CODE NOT IN('FC')
GROUP BY A.EMPLOYEE_CODE
UNION
SELECT A.EMPLOYEE_CODE, AMOUNT FROM FOOD_COUPON A, PAY_ELEMENT B
WHERE EMPLOYEE_CODE=EMP.EMPLOYEE_CODE
AND B.PAY_ELEMENT_CODE=A.PAY_ELEMENT_CODE
AND B.PAY_ELEMENT_TYPE='E'
AND PERIOD=88)D
WHERE EMPLOYEE_CODE=EMP.EMPLOYEE_CODE) AS EARNINGS,
(SELECT SUM(AMOUNT) FROM(
SELECT A.EMPLOYEE_CODE, SUM(A.AMOUNT) AS AMOUNT FROM PAYROLL A, PAY_ELEMENT B
WHERE A.PAY_ELEMENT_CODE=B.PAY_ELEMENT_CODE AND
A.PERIOD= 88 AND A.EMPLOYEE_CODE=EMP.EMPLOYEE_CODE AND B.PAY_ELEMENT_TYPE='D'
AND B.PAY_ELEMENT_CODE NOT IN('FCD')
GROUP BY A.EMPLOYEE_CODE
UNION
SELECT A.EMPLOYEE_CODE, AMOUNT FROM FOOD_COUPON A, PAY_ELEMENT B
WHERE EMPLOYEE_CODE=EMP.EMPLOYEE_CODE
AND B.PAY_ELEMENT_CODE=A.PAY_ELEMENT_CODE
AND B.PAY_ELEMENT_TYPE='D'
AND PERIOD=88)D
WHERE EMPLOYEE_CODE=EMP.EMPLOYEE_CODE) AS DEDUCTIONS,
NVL((SELECT AMOUNT FROM PAY WHERE PAY_ELEMENT_CODE='BSC' AND EMPLOYEE_CODE=EMP.EMPLOYEE_CODE),0)AS BASIC,
NVL((SELECT AMOUNT FROM PAY WHERE PAY_ELEMENT_CODE='HRA' AND EMPLOYEE_CODE=EMP.EMPLOYEE_CODE),0)AS HRA,
NVL((SELECT AMOUNT FROM PAY WHERE PAY_ELEMENT_CODE='SP2' AND EMPLOYEE_CODE=EMP.EMPLOYEE_CODE),0)AS SPECIALPAY2,
NVL((SELECT NVL(AMOUNT,0) FROM PAY WHERE PAY_ELEMENT_CODE='OA' AND EMPLOYEE_CODE=EMP.EMPLOYEE_CODE),0)AS OTHERALLOW,
NVL((SELECT AMOUNT FROM PAY WHERE PAY_ELEMENT_CODE='TA' AND EMPLOYEE_CODE=EMP.EMPLOYEE_CODE),0)AS TRANSALLOW,
NVL((SELECT AMOUNT FROM PAY WHERE PAY_ELEMENT_CODE='FC' AND EMPLOYEE_CODE=EMP.EMPLOYEE_CODE),0)AS FOODCOUPONS
FROM "EMPLOYEE" "EMP",
"DEPARTMENT" "DEPT",
"DIVISION" "DIV",
"LOCATION" "LOC",
"LEAVE_BALANCE" "L",
"PAYROLL" ,
"ATTENDANCE" "A"
WHERE ( "EMP"."DEPARTMENT_CODE" = "DEPT"."DEPARTMENT_CODE" ) and
( "EMP"."DIVISION_CODE" = "DEPT"."DIVISION_CODE" ) and
( "EMP"."DIVISION_CODE" = "DIV"."DIVISION_CODE" ) and
( "EMP"."LOCATION_CODE" = "LOC"."LOCATION_CODE" ) and
( "EMP"."EMPLOYEE_CODE" = "L"."EMPLOYEE_CODE" ) and
( "DIV"."DIVISION_CODE" = "L"."DIVISION_CODE" ) and
( "L"."EMPLOYEE_CODE" = "PAYROLL"."EMPLOYEE_CODE" ) and
( "PAYROLL"."DIVISION_CODE" = "L"."DIVISION_CODE" ) and
( ( "EMP"."CURRENT_STATUS" = 'C' ) AND
( "PAYROLL"."PAY_ELEMENT_CODE" = 'BSC' ) AND
( "PAYROLL"."PERIOD" = 88) AND
("EMP"."EMPLOYEE_CODE"="A"."EMPLOYEE_CODE") AND
("A"."PERIOD"=88))
The above query returs rows in Standard Edition but throws error in XE with the same table structure and same data.
Kindly help me in this regard,
Vijayaraghavan K



CREATE TABLE "DBO"."ATTENDANCE"
( "EMPLOYEE_CODE" VARCHAR2(6
BYTE) NOT NULL ENABLE,
"PERIOD"
VARCHAR2(7 BYTE) NOT NULL ENABLE,
"DIVISION_CODE"
NUMBER(2,0) NOT NULL ENABLE,
"PUBLIC_HOLIDAYS"
NUMBER(2,0),
"WEEKLY_HOLIDAYS"
NUMBER(2,0),
"CASUAL_LEAVE"
NUMBER(5,2),
"EARNED_LEAVE"
NUMBER(5,2),
"ON_DUTY"
NUMBER(5,2),
"SICK_LEAVE"
NUMBER(5,2),
"ESI_LEAVE"
NUMBER(5,2),
"LOSS_OF_PAY_DAYS"
NUMBER(5,2),
"CANTEEN_DAYS"
NUMBER(5,2),
"WORKING_DAYS"
NUMBER(5,2),
"ATTENDED_DAYS"
NUMBER(5,2),
"PAID_DAYS"
NUMBER(5,2),
"AUTHORIZATION_TAG"
VARCHAR2(1 BYTE),
"CREATED_BY"
VARCHAR2(8 BYTE),
"CREATED_DATE"
DATE,
"LAST_MODIFIED_BY"
VARCHAR2(8 BYTE),
"LAST_MODIFIED_DATE"
DATE,
CONSTRAINT "PK_ATTENDANCE" PRIMARY
KEY ("EMPLOYEE_CODE", "PERIOD")
CONSTRAINT "ATTENDANCE_EMPLOYEE_FK1"
FOREIGN KEY ("EMPLOYEE_CODE")
REFERENCES
"DBO"."EMPLOYEE" ("EMPLOYEE_CODE") ENABLE
===============================================================
CREATE TABLE "DBO"."DEPARTMENT"
( "DIVISION_CODE" NUMBER(2,0)
NOT NULL ENABLE,
"DEPARTMENT_CODE"
NUMBER(3,0) NOT NULL ENABLE,
"DESCRIPTION"
VARCHAR2(60 BYTE) NOT NULL ENABLE,
"CREATED_BY"
VARCHAR2(8 BYTE),
"CREATED_DATE"
DATE,
"LAST_MODIFIED_BY"
VARCHAR2(8 BYTE),
"LAST_MODIFIED_DATE"
DATE,
CONSTRAINT "PK_DEPARTMENT" PRIMARY
KEY ("DIVISION_CODE", "DEPARTMENT_CODE")
CONSTRAINT "FK_DEPARTMENT_DIVISION"
FOREIGN KEY ("DIVISION_CODE")
REFERENCES
"DBO"."DIVISION" ("DIVISION_CODE") ON DELETE
CASCADE ENABLE
===============================================================
CREATE TABLE "DBO"."DIVISION"
( "DIVISION_CODE" NUMBER(2,0)
NOT NULL ENABLE,
"COMPANY_CODE"
NUMBER(2,0),
"DESCRIPTION"
VARCHAR2(30 BYTE) NOT NULL ENABLE,
"ADDRESS1"
VARCHAR2(200 BYTE),
"ADDRESS2"
VARCHAR2(30 BYTE),
"ADDRESS3"
VARCHAR2(30 BYTE),
"LOCATION"
VARCHAR2(30 BYTE),
"PINCODE"
NUMBER(6,0),
"PHONE"
VARCHAR2(20 BYTE),
"EMAIL_ID"
VARCHAR2(40 BYTE),
"FAX"
VARCHAR2(20 BYTE),
"UNIT_HEAD_DESIG"
VARCHAR2(30 BYTE),
"UNIT_HEAD_NAME"
VARCHAR2(30 BYTE),
"FINANCE_HEAD_DESIG"
VARCHAR2(30 BYTE),
"FINANCE_HEAD_NAME"
VARCHAR2(30 BYTE),
"HRS_HEAD_DESIG"
VARCHAR2(30 BYTE),
"HRS_HEAD_NAME"
VARCHAR2(30 BYTE),
"PROCUREMENT_MEMBER1"
VARCHAR2(30 BYTE),
"PROCUREMENT_MEMBER2"
VARCHAR2(30 BYTE),
"PROCUREMENT_MEMBER3"
VARCHAR2(30 BYTE),
"PAN_NO"
VARCHAR2(20 BYTE),
"GST_NO"
VARCHAR2(20 BYTE),
"CST_NO"
VARCHAR2(20 BYTE),
"CONTRA_GL_CODE"
NUMBER(6,0),
"ECC_CODE"
VARCHAR2(20 BYTE),
"ESI_NO"
VARCHAR2(15 BYTE),
"PF_NO"
VARCHAR2(15 BYTE),
"PROFESSIONAL_TAX_NO"
VARCHAR2(15 BYTE),
"SALES_TAX_NO"
VARCHAR2(15 BYTE),
"CREATED_BY"
VARCHAR2(8 BYTE),
"CREATED_DATE"
DATE,
"LAST_MODIFIED_BY"
VARCHAR2(8 BYTE),
"LAST_MODIFIED_DATE"
DATE,
"COMPANY_ID"
CHAR(3 BYTE),
"NAME"
VARCHAR2(30 BYTE),
"PIN_CODE"
NUMBER(6,0),
"PHONE_NUMBER"
VARCHAR2(20 BYTE),
"FAX_NUMBER"
VARCHAR2(20 BYTE),
"PAN_NUMBER"
VARCHAR2(20 BYTE),
"GST_NUMBER"
VARCHAR2(20 BYTE),
"CST_NUMBER"
VARCHAR2(20 BYTE),
"TAN_NO"
VARCHAR2(20 BYTE),
"STATUS"
VARCHAR2(1 BYTE),
CONSTRAINT "PK_DIVISION_CODE"
PRIMARY KEY ("DIVISION_CODE")
CONSTRAINT "FK_COMPANY_CODE" FOREIGN
KEY ("COMPANY_CODE")
REFERENCES
"DBO"."COMPANY" ("COMPANY_CODE") ON DELETE
CASCADE ENABLE
==============================================================
CREATE TABLE
"DBO"."EMPLOYEE"
( "EMPLOYEE_CODE" VARCHAR2(6
BYTE) NOT NULL ENABLE,
"NAME"
VARCHAR2(30 BYTE) NOT NULL ENABLE,
"EMPLOYEE_INITIALS"
VARCHAR2(3 BYTE),
"FH_NAME"
VARCHAR2(30 BYTE) NOT NULL ENABLE,
"BIRTH_DATE"
DATE NOT NULL ENABLE,
VARCHAR2(1 BYTE) NOT NULL ENABLE,
"STATUS"
VARCHAR2(1 BYTE) NOT NULL ENABLE,
"BLOOD_GROUP"
VARCHAR2(15 BYTE),
"ADDRESS"
VARCHAR2(30 BYTE),
"STREET"
VARCHAR2(30 BYTE),
"EMAIL"
VARCHAR2(30 BYTE),
"CITY"
VARCHAR2(30 BYTE),
"STATE"
VARCHAR2(30 BYTE),
"PINCODE"
VARCHAR2(6 BYTE),
"COUNTRY"
VARCHAR2(20 BYTE),
"PHONE"
VARCHAR2(15 BYTE),
"QUALIFICATION"
VARCHAR2(30 BYTE) NOT NULL ENABLE,
"DESIGNATION"
VARCHAR2(30 BYTE) NOT NULL ENABLE,
"GRADE"
VARCHAR2(2 BYTE),
"SUPERVISOR_CODE"
VARCHAR2(6 BYTE),
"CATEGORY_CODE"
VARCHAR2(2 BYTE) NOT NULL ENABLE,
"SUB_CATEGORY_CODE"
VARCHAR2(2 BYTE) NOT NULL ENABLE,
"SUB_CATEGORY_TYPE"
VARCHAR2(1 BYTE),
"DEPARTMENT_CODE"
NUMBER(3,0) NOT NULL ENABLE,
"LOCATION_CODE"
VARCHAR2(3 BYTE) NOT NULL ENABLE,
"DIVISION_CODE"
NUMBER(2,0) NOT NULL ENABLE,
"COST_CODE"
VARCHAR2(4 BYTE),
"JOINING_DATE"
DATE NOT NULL ENABLE,
"PROBATION_DATE"
DATE,
"CONFIRMATION_DATE"
DATE,
"PROMOTION_DATE"
DATE,
"TERMINATION_DATE"
DATE,
"TERMINATION_REASON"
VARCHAR2(30 BYTE),
"CURRENT_STATUS"
VARCHAR2(1 BYTE),
"MAX_CASUAL_LEAVE"
NUMBER(5,2),
"MAX_EARNED_LEAVE"
NUMBER(5,2),
"MAX_MEDICAL_LEAVE"
NUMBER(5,2),
"MONTH_OF_INCREMENT"
VARCHAR2(3 BYTE),
"NO_OF_INCREMENT"
NUMBER(2,0),
"LAST_INCREMENT_MONTH"
VARCHAR2(3 BYTE),
"PAN_NO"
VARCHAR2(15 BYTE),
"PF_NO"
VARCHAR2(15 BYTE),
"PF_PERCENTAGE"
NUMBER,
"VOLUNTARY_PF_PERCENTAGE"
NUMBER(3,0),
"PF_DATE"
DATE,
"ESI_INDICATOR"
VARCHAR2(1 BYTE),
"ESI_NO"
VARCHAR2(15 BYTE),
"ESI_DATE"
DATE,
"ESI_DISPENSARY"
VARCHAR2(30 BYTE),
"MODE_OF_PAYMENT"
VARCHAR2(3 BYTE),
"BANK_CODE"
VARCHAR2(3 BYTE),
"BANK_AC_NO"
VARCHAR2(15 BYTE),
"BRANCH_CODE"
VARCHAR2(3 BYTE),
"CREATED_BY"
VARCHAR2(8 BYTE),
"CREATED_DATE"
DATE,
"LAST_MODIFIED_BY"
VARCHAR2(8 BYTE),
"LAST_MODIFIED_DATE"
DATE,
"SAF_CODE"
VARCHAR2(30 BYTE),
"GSAF_CODE"
VARCHAR2(30 BYTE),
"IMAGE_LINK"
VARCHAR2(200 BYTE),
"PHONE_MOBILE"
VARCHAR2(15 BYTE),
CONSTRAINT "PK_EMP" PRIMARY KEY
("EMPLOYEE_CODE")
CONSTRAINT "FK_EMPLOYEE_CATEGORY"
FOREIGN KEY ("CATEGORY_CODE")
REFERENCES
"DBO"."CATEGORY" ("CATEGORY_CODE") ENABLE,
CONSTRAINT "FK_EMPLOYEE_DEPARTMENT"
FOREIGN KEY ("DIVISION_CODE", "DEPARTMENT_CODE")
REFERENCES
"DBO"."DEPARTMENT" ("DIVISION_CODE", "DEPARTMENT_CODE")
ON DELETE CASCADE ENABLE,
CONSTRAINT "FK_EMPLOYEE_DIVISION"
FOREIGN KEY ("DIVISION_CODE")
REFERENCES
"DBO"."DIVISION" ("DIVISION_CODE") ENABLE,
CONSTRAINT "FK_EMPLOYEE_LOCATION"
FOREIGN KEY ("LOCATION_CODE")
REFERENCES "DBO"."LOCATION"
("LOCATION_CODE") ENABLE,
CONSTRAINT "FK_EMPLOYEE_SUBCATEGORY"
FOREIGN KEY ("SUB_CATEGORY_CODE")
REFERENCES
"DBO"."SUB_CATEGORY" ("SUB_CATEGORY_CODE") ENABLE
===============================================================
CREATE TABLE "DBO"."FOOD_COUPON"
( "PAY_ELEMENT_CODE" VARCHAR2(3
BYTE),
"EMPLOYEE_CODE"
VARCHAR2(6 BYTE),
"PERIOD"
VARCHAR2(7 BYTE),
"AMOUNT"
NUMBER(10,2),
"CREATED_BY"
VARCHAR2(8 BYTE),
"CREATED_DATE"
DATE,
"LAST_MODIFIED_BY"
VARCHAR2(8 BYTE),
"LAST_MODIFIED_DATE"
DATE,
CONSTRAINT "FD_PAY_ELEMENT" FOREIGN
KEY ("PAY_ELEMENT_CODE")
REFERENCES
"DBO"."PAY_ELEMENT" ("PAY_ELEMENT_CODE") ENABLE,
CONSTRAINT "FD_EMPLOYEE_CODE"
FOREIGN KEY ("EMPLOYEE_CODE")
REFERENCES
"DBO"."EMPLOYEE" ("EMPLOYEE_CODE") ENABLE
==========================================================
CREATE TABLE
"DBO"."LEAVE"
( "EMPLOYEE_CODE" VARCHAR2(6
BYTE) NOT NULL ENABLE,
"LEAVE_CODE"
VARCHAR2(2 BYTE) NOT NULL ENABLE,
"LEAVE_FROM_DATE"
DATE NOT NULL ENABLE,
"LEAVE_TO_DATE"
DATE NOT NULL ENABLE,
"LEAVE_FROM_SESSION"
VARCHAR2(1 BYTE),
"LEAVE_TO_SESSION"
VARCHAR2(1 BYTE),
"LEAVE_REQUISITION_DATE"
DATE,
"LEAVE_DAYS"
NUMBER(3,1),
"LOP_DAYS"
NUMBER(4,1),
"SIGNED_BY"
VARCHAR2(6 BYTE),
"SANCTIONED_BY"
VARCHAR2(6 BYTE),
"LEAVE_REASON"
VARCHAR2(100 BYTE),
"PUBLIC_HOLIDAYS"
NUMBER(2,0),
"WEEKLY_HOLIDAYS"
NUMBER(2,0),
"PERIOD"
VARCHAR2(7 BYTE),
"AUTHORIZATION_TAG"
VARCHAR2(1 BYTE),
"CREATED_BY"
VARCHAR2(8 BYTE),
"CREATED_DATE"
DATE,
"LAST_MODIFIED_BY"
VARCHAR2(8 BYTE),
"LAST_MODIFIED_DATE"
DATE,
CONSTRAINT "PK_LEAVE" PRIMARY KEY
("EMPLOYEE_CODE", "LEAVE_CODE",
"LEAVE_FROM_DATE", "LEAVE_TO_DATE")
CONSTRAINT "SYS_C0037897" FOREIGN
KEY ("SANCTIONED_BY")
REFERENCES "DBO"."EMPLOYEE"
("EMPLOYEE_CODE") ON DELETE CASCADE DISABLE,
CONSTRAINT "SYS_C0037898" FOREIGN
KEY ("EMPLOYEE_CODE")
REFERENCES
"DBO"."EMPLOYEE" ("EMPLOYEE_CODE") ON DELETE
CASCADE DISABLE,
CONSTRAINT "SYS_C0037899" FOREIGN
KEY ("SIGNED_BY")
REFERENCES "DBO"."EMPLOYEE"
("EMPLOYEE_CODE") ON DELETE CASCADE DISABLE,
FOREIGN KEY ("LEAVE_CODE")
REFERENCES
"DBO"."LEAVE_TYPE" ("LEAVE_CODE") ON DELETE
CASCADE ENABLE
===============================================================
CREATE TABLE "DBO"."LEAVE_BALANCE"
( "EMPLOYEE_CODE" VARCHAR2(6
BYTE) NOT NULL ENABLE,
"DIVISION_CODE"
NUMBER(2,0),
"EL_BALANCE"
NUMBER(6,2),
"CL_BALANCE"
NUMBER(6,2),
"ML_BALANCE"
NUMBER(6,2),
"ADJ_PAISE"
NUMBER(2,0),
"CREATED_BY"
VARCHAR2(8 BYTE),
"CREATED_DATE"
DATE,
"LAST_MODIFIED_BY"
VARCHAR2(8 BYTE),
"LAST_MODIFIED_DATE"
DATE,
"YEAR"
NUMBER(4,0),
CONSTRAINT "PK_LEAVE_BALANCE"
PRIMARY KEY ("EMPLOYEE_CODE")
CONSTRAINT
"FK_LEAVE_BALANCE_DIVISION" FOREIGN KEY ("DIVISION_CODE")
REFERENCES "DBO"."DIVISION"
("DIVISION_CODE") ON DELETE CASCADE ENABLE,
CONSTRAINT "SYS_C0037900" FOREIGN
KEY ("EMPLOYEE_CODE")
REFERENCES
"DBO"."EMPLOYEE" ("EMPLOYEE_CODE") ON DELETE
CASCADE DISABLE
========================================================
CREATE TABLE "DBO"."PAY"
( "EMPLOYEE_CODE" VARCHAR2(6
BYTE) NOT NULL ENABLE,
"PAY_ELEMENT_CODE"
VARCHAR2(3 BYTE) NOT NULL ENABLE,
"AMOUNT"
NUMBER(10,2) NOT NULL ENABLE,
"CREATED_BY"
VARCHAR2(8 BYTE),
"CREATED_DATE"
DATE,
"LAST_MODIFIED_BY"
VARCHAR2(8 BYTE),
"LAST_MODIFIED_DATE"
DATE,
CONSTRAINT "PK_PAY" PRIMARY KEY
("EMPLOYEE_CODE", "PAY_ELEMENT_CODE")
CONSTRAINT "FK_PAY_EMPLOYEE_CODE"
FOREIGN KEY ("EMPLOYEE_CODE")
REFERENCES
"DBO"."EMPLOYEE" ("EMPLOYEE_CODE") ENABLE,
CONSTRAINT "FK_PAY_PAYELEMENT"
FOREIGN KEY ("PAY_ELEMENT_CODE")
REFERENCES
"DBO"."PAY_ELEMENT" ("PAY_ELEMENT_CODE") ON
DELETE CASCADE ENABLE
================================================ ======
CREATE TABLE "DBO"."PAY_ELEMENT"
( "PAY_ELEMENT_CODE" VARCHAR2(3
BYTE) NOT NULL ENABLE,
"DESCRIPTION"
VARCHAR2(30 BYTE) NOT NULL ENABLE,
"PAY_ELEMENT_TYPE"
VARCHAR2(1 BYTE) NOT NULL ENABLE,
"PARTIAL_INDICATOR"
VARCHAR2(1 BYTE),
"TAX_INDICATOR"
VARCHAR2(1 BYTE),
"CREATED_BY"
VARCHAR2(8 BYTE),
"CREATED_DATE"
DATE,
"LAST_MODIFIED_BY"
VARCHAR2(8 BYTE),
"LAST_MODIFIED_DATE"
DATE,
"SEQUENCE_NO"
NUMBER(2,0),
CONSTRAINT "PK_PAY_ELEMENT" PRIMARY
KEY ("PAY_ELEMENT_CODE")
=======================================================
CREATE TABLE "DBO"."PAYROLL"
( "EMPLOYEE_CODE" VARCHAR2(6
BYTE) NOT NULL ENABLE,
"PAY_ELEMENT_CODE"
VARCHAR2(3 BYTE) NOT NULL ENABLE,
"PERIOD"
VARCHAR2(7 BYTE) NOT NULL ENABLE,
"AMOUNT"
NUMBER(10,2) NOT NULL ENABLE,
"DIVISION_CODE"
NUMBER(2,0) NOT NULL ENABLE,
"SERIAL_CODE"
NUMBER(2,0),
"AUTHORIZATION_TAG"
VARCHAR2(1 BYTE),
"CREATED_BY"
VARCHAR2(8 BYTE),
"CREATED_DATE"
DATE,
"LAST_MODIFIED_BY"
VARCHAR2(8 BYTE),
"LAST_MODIFIED_DATE"
DATE,
CONSTRAINT "SYS_C0037906" FOREIGN
KEY ("EMPLOYEE_CODE")
REFERENCES
"DBO"."EMPLOYEE" ("EMPLOYEE_CODE") ON DELETE
CASCADE DISABLE
============================================================
these are the Table structures
Please help me in this regard

Limitations of Oracle 11g

I was just wondering what kind of limitations the free version of Oracle 11g has. How many computers can be connected to it the DB? Is there a size limit of the DB. Does it work over a VPN? I want to use it for a small company with about 15 computers I just want to know what limitations it has?

Hello,
I have downloaded the Oracle 11g Enterprise editionFor commercial or production purpose Enterprise Edition is not free of charge, but may be some Asteroïd has just impacted the Earth :-) ...
You may review the OTN License Agreement:
http://www.oracle.com/technetwork/licenses/standard-license-152015.html
The following may be interesting:
LICENSE RIGHTS
We grant you a nonexclusive, nontransferable limited license to use the programs only for the purpose of developing, testing, prototyping and demonstrating your application, and not for any other purpose. If you use the application you develop under this license for any internal data processing or for any commercial or production purposes, or you want to use the programs for any purpose other than as permitted under this agreement, you must obtain a production release version of the program by contacting us or an Oracle reseller to obtain the appropriate license.For small business, Standard Edition One may be a good choice and is rather cheap (about 180 US$/User Named License).
Hope this help.
Best regards,
Jean-Valentin
Edited by: Lubiez Jean-Valentin on Feb 27, 2011 9:48 AM

Shell Limits for Oracle DB 10g under SLES 9

Hi.
We installed SLES 9 and want to install now Oracle DB 10g R2.
We are at configuring Linux for the installation process using this guide: http://www.oracle.com/technology/pub/articles/smiley_10gdb_install.html#shell
At the linked part (shell limits) is explained how to set the shell limits for the user oracle. And there are two parts, one for SLES9 and one for RHEL4.
But the files profile.local and csh.login.local are not existing! But the files from the RHEL4 section (profile and csh.login) exists.
Is this a failure in the guide? Are the two parts from RHEL4 and SLES9 switched?
Or it is right that we have to create these files by setting these shell limits??
Thanks for answering.

Hi.
I usually create these files on the Suse box. These files are never there on either x86, ia64 og x86(64).
rgds
Kjell

Setting Resource limits for Oracle user in 11gR2

HI Friends,
I am using Oracle Database 11g R2 on windows.
My Application connects to the database using a schema (user1). Some times the application user sessions makes the Database usage / CPU/ IO high and affecting the performance of the Database.
I would like to set some Limits on the Resource usage (Database and System resources) for those Application user schema (user1) to avoid the bottleneck on the Database and Server without affecting the usage of the Application on Transactions.
How can i achieve it?
Regards,
DB

839396 wrote:
HI Friends,
I am using Oracle Database 11g R2 on windows.
My Application connects to the database using a schema (user1). Some times the application user sessions makes the Database usage / CPU/ IO high and affecting the performance of the Database.
I would like to set some Limits on the Resource usage (Database and System resources) for those Application user schema (user1) to avoid the bottleneck on the Database and Server without affecting the usage of the Application on Transactions.
How can i achieve it?
Regards,
DBis application 3-tier like below?
EndUser<=>browser<=>WebServer<=>ApplicationServer<=>DatabaseServer

Practical limits of Oracle RAC

Hi Guys,
Can anyone tell me if Oracle RAC has a limitation terms on how many hosts can be added to the cluster? Either in terms of what the product supports or as a practical limitation.
I don't have a particular need to know - I'm just curious :-)
Many thanks
S

As close and far as I know , the number is mostly limited by the clusterware used.
Plenty of informations about this is @metalink in 220970.1 RAC: Frequently Asked Questions

Database limits of oracle lite

Could anyone please tell me the database limits(eg table
size,number of columns etc) of oracle8i lite
Thanks,
Debu

So - you are using Oracle Application Express to interact with the data stored in your Oracle Database - Express Edition.
The only limits in the database Express Edition are:
- it will not use more than 1 CPU
- it will not use more than 1 GB RAM
- it will not permit more than 4GB user data to be stored
Any other limits or limitations are from the application (or application design) or from Application Express. You might want to move this discussion to either the Application Express forum or the Express Edition forum. (Both available from http://forums.oracle.com but you need to register for the Express Edition forum, as shown on the XE home page.)

Regarding limits in oracle 8

Hey guys, i need your experience here;)
We use oracle 8, and today some customers reported that regarding a table (financial one... ouch) all the entries they did since the 23rd october dont appear, the lines are blank , but incremented
is there a limit to the number of datas ? entries?
should i do a purge of the tables ( it has never been done before.; and i took the job 3 weeks ago so i dont know all the history ;) )
all the help you can provide will be real helpful guys
in advance thx

Limits? Entries? Purge?
Don't do anything rash.
If you don't know what you're doing or why you're doing it, action for the sake of action will probably just cause more issues.
There's not enough information for anyone to diagnose the problem.
Whilst an upgrade to a supported should be a priority target in the longer term, in the immediate term, why is it likely to solve the problem?
You need to gather evidence, try to reproduce the problem and get to the root cause.
If it was an Oracle bug then yes, you're going to wish you were on a supported version but it's more likely to be something else.
Start with the evidence you've got.
These "blank" rows in the database. How have you determined that they are blank?
"blank but incremented" what does that mean?
Edited by: DomBrooks on Nov 3, 2010 11:33 AM

Wanted to know cursor limitations in oracle

Hi all,
I want to know what are the limitations of cursors in terms of sql
I am getting error when for the following procedures......
1.
create or replace procedure test is
Cursor Cur_SecRes is
select secresdesc,secrescode from
(SELECT SECRESDESC,secrescode FROM SECONDARYRES group BY secrescode asc, SECRESDESC desc)
WHERE ROWNUM=1;
Begin
for x in Cur_SecRes
loop
dbms_output.put_line(x.secrescode | | ' ,' | | x.secresdesc);
end loop;
End;
The above procedure is opens the top q query, which is required for imporving performance. The query is running in Sql Plus, but if I include the query in PL sql block it is giving error.
Is there any way out for running the above query, If any body knows then please let me know at [email protected]
Similarly the second procedure is giving error......
2.
create or replace procedure test is
Cursor Cur_SecRes is
SELECT SECRESDESC,secrescode FROM SECONDARYRES order BY SECRESDESC desc,secrescode
union all
SELECT priRESDESC,prirescode FROM priONDARYRES order BY SECRESDESC desc,secrescode;
begin
for x in Cur_SecRes
loop
dbms_output.put_line(x.secrescode | | ' ,' | | x.secresdesc);
end loop;
end;
overall I need to know the limitations of cursor or pl sql block,
Thanks in advance.....
Regards,
sudhakar

Hi Sudhakar
What is exactly the error you are getting ?
It could be a privilege problem. Are you (the creator of the procedure) the owner of the table SECONDARYRES ? If not, then you have to get the select privilege on the table via a direct grant (GRANT SELECT ON SECONDARYRES TO xxxx) and not via a ROLE.
PL/SQL does not recognize privileges received over a role, but SQL does !
The procedure itself and the cursor looks ok for me.
Hope to help
Guido

APPROVAL LIMITS IN ORACLE RECEIVABLES

Whilst in the AR Corporate Super User responsibility in Vision Operations, I defined approval limits for a an application user with a currency of GBP and an amount ranging from £5000 to£6000 and then saved it. Later, I then decided that I wanted to change the amounts from lets say £10,000 to £20,000. Whwn I call up the user in the Approval limits window in AR and I try to click in the currency filed I get the following message:
APPS_AR_11290 The approval limit for the user (eg Fred)for the currency GBP already exists. How do I change the amounts
and what reports can I run to see the various users and their approval limits? please advise me

Hi,
For your current requirement please follow the below procedure.
1. Disable the Automatic Transaction Numbering In the Transaction Window.
Navigation: Receivables Manager --> Setup --> Transactions --> Sources.
In the transactions sources window Disable the Automatic Transaction Numbering.
Now we are able to create the transactions with alphabetical numbering.
Regards.
Raju.

SGA_MAX_SIZE limitations in Oracle 9i

Similar Messages

Maybe you are looking for