Warning ORA-01002, ORA-06502 AND ORA-12899
Hi All,
When iam executing my mapping iam facing the following warninigs.
Name Status Log
MAP_ Warning CursorFetchMapTerminationRTV20007
MAP_ Warning ORA-01002: fetch out of sequence
ORA-02063: preceding line from link
MAP_Warning ORA-06502: PL/SQL: numeric or value error: character string buffer too small
MAP_Warning ORA-12899: value too large for column %s (actual: %s, maximum: %s)
ORA-02063: preceding line from link
Further to inform you that, in source and target the data type size is same.
How can i resolve it
Thanks in advance.
I mean to say select while executing it from Database you can pin-point the exact line which cause error.
cheers
Nawneet
Similar Messages
-
Help - I'm getting errors ORA-06502:and ORA-01002: at runtime
Help
I am getting the following errors at runtime and need some isdeas on what to check:
ORA-06502: PL/SQL: numeric or value error: character string buffer too small
ORA-06512: at "OWB_RUNTIME.WB_RT_MAPAUDIT", line 1736
ORA-06512: at "OWB_RUNTIME.WB_RT_MAPAUDIT", line 2625
ORA-06512: at "OWB_TARGET.MAP_BSL_PLACEMENT_FACT2B", line 1148
ORA-01002: fetch out of sequence
ORA-02063: preceding line from BASIL@LOC_TARGET_NEW_LOC_BASIL_SOURC
ORA-06512: at "OWB_TARGET.MAP_BSL_PLACEMENT_FACT2B", line 1457
ORA-06512: at "OWB_TARGET.MAP_BSL_PLACEMENT_FACT2B", line 3458
ORA-06512: at line 1
My Mapping is a fact recording enrolments in courses (located in my main target database - oracle 9i)
joining with an equi-join to a table that contains an audit of all changes to the enrolment (in my source database - Sybase 12.5)
then updating two fields in a tabke that is a second definition of the first fact
The equi join uses the key to the enrolment table, plus a transaction type to identify only the creation of the record
Between the join and the update of the table one field is going thru a trim (converting char to varchar2) then an expression that sets the value to "not_supplied" for cases where the value was null.
The other field is a date (from sybase datetime to oracle Date)
(they are the user that created the enrolment and the date the enrolment was actioned)
I created this mapping by copying another mapping that does pretty much the same thing, deleting the join and table it was joining to and adding the audit table and new join.
Both mapping deploy fine with no warnings, the original executes fine the variation gives the errors above.
I have tried removing one then the other of the columns I am updating. (the same errors occur)
I am about to re-write the mapping from scratch, but can anyone guess what is wrong with it ? (I'm using OWB 9.2.0.2.8)Thanks for the suggestion
There are no "char(32767)"s in the package - altho there are "varchar2(32767)"s
I have tried a variotion on the script, outputting the result to a new table instead of updating the enrolment - which ran fine so the error is in the update.
I tried adding a step using the result in the temp table to update the enrolment table - and got my errors again. So there is something funny in my data. Nothing obvious shows.
The full temp table contains 745292 records - when it failed 150 records had been written.
I note that although I had expected only to find one record per enrolment, there are some where there are two (@#$%!! source system writing two "insert" audit records) - could my problem be that I am updating a record previously updated - where do I set the script to commit as it goes?
Sandra -
4.0 ORA-06502 and ORA-01722 in different languages
Hi!
After 4.0 installation on my XE-database there are some errors - dependig on which language is actual.
german language is actual:
home > administration > dashboard:
every report results ORA-01722
english language is actual:
home:
report about top applications results
ORA-06502: PL/SQL: numeric or value error ORA-06512: at "APEX_040000.WWV_FLOW_4000_UI", line 731 ORA-06502: PL/SQL: numeric or value error: character to number conversion error
Is there any idea about what is wrong?
Kind regards,
AndreaHi Andrea,
I see similar errors on my instance. I updated to 4.0.1 and saw some of them disappear, but a few of them are still there. Even reinstalling 4.0.1 from scratch did not change anything about this.
Apparently the de-translation has some gaps, e.g. the title for the worspace administration is
"Workspace &COMPANY verwalten." where &COMPANY should be the workspacename, or the confirmation message when deleting an application, which says "Anwendung &F4000_P20_FLOW_ID wurde gelöscht.". Both messages appear with the correct substitution value as soon as I switch the language to English.
What made me wonder at first wass that both dashboards for "Top Applications" and "Top Users" worked in German, but threw erros in the English version. Without changing anything in my system they "started" working later, so I guess there was a problem with the proper initialization for those reports.
I still have a complete set of ORA-01722 in the German version of the activity dashboard, which works better in English:
Top Users, Top Applications and Top Pages say "Report contains no data", which is better than ORA-01722. Recent Logins shows correct results, Recent errors gives me the 01722-errors I produced before.
Does anyone else have these problems? Or does anyone have a solution for them? -
ORA-06502 and ORA-06503 if more than 3700 rows
In a simple application one of the two tables has about 10.000 rows. If I limit the "Max Row Count" to 3700 the "select list" will be generated without error
("row(s) 1-17 of more than 3700").
With "Max Row Count" 3710 and 3720 an ORA-06502, with "Max Row Count" 3730 an ORA-06503 occur and no select list will appear.
Other values greater 3710 e.g. 4000 don't cause any Oracle error but no select list was built.
It seems to be that the value limit will be exeeded in cases where the row count is greater than 3700.Joachim,
Select lists are limited to 32,000 characters. This includes the select and option tags and all the display and return values. Depending on your pagination settings, specifically on the number of rows you display on each page, this translates into around 4000 rows being supported by this particular pagination style. If you have more rows then that, I'd recommend using a different pagination style, one that does not show a select list.
Regards,
Marc -
ORA-12505, TNS:listener and ORA-12514: TNS:listener
All,
Connecting to the database through the SQL Developer is giving me the error "ORA-12505, TNS:listener does not currently know of SID given in connect descriptor"
Database version : Oracle 10g XE
O/S : Windows 7, 32 bit
I have restarted my machine and tried but no luck. Tried from sqlplus also and the error was
ERROR:
ORA-12514: TNS:listener does not currently know of service requested in connect
descriptor"
Please provide me the steps to check and resolve this issue.
Thank you very much in advance.
ThanksHere is what I have in my tnsnames.ora file
XE =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = TCP)(HOST = MSPL-08-09-D169.MSFTPNQ.com)(PORT = 1521))
(CONNECT_DATA =
(SERVER = DEDICATED)
(SERVICE_NAME = XE)
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_XE))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
ORACLR_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC_FOR_XE))
(CONNECT_DATA =
(SID = CLRExtProc)
(PRESENTATION = RO)
Database name is 'XE' -
ORA-17002 and ORA-17009 while calling Stored Procedures
Hi,
We are developing a JDBC application using WebLogic 6.0 as AppServer. When we
rolled out the application in production, things work fine for about a day or
so, then calls to Stored Procedures start giving ORA-17002 (io exception) and
ORA-17009 (Closed Statement) exceptions while calling Stored Procedures. Restarting
the server 'fixes' the problem for one more day.... We are not able to reproduce
this behaviour in test or development servers.
Can anybody suggest something.....
Regards,
Usman.Usman wrote:
>
Hi,
We are developing a JDBC application using WebLogic 6.0 as AppServer. When we
rolled out the application in production, things work fine for about a day or
so, then calls to Stored Procedures start giving ORA-17002 (io exception) and
ORA-17009 (Closed Statement) exceptions while calling Stored Procedures. Restarting
the server 'fixes' the problem for one more day.... We are not able to reproduce
this behaviour in test or development servers.
Can anybody suggest something.....
Regards,
Usman.Hi. Describe how you are obtaining and using pool connections. Also, do download the
latest thin driver from Oracle, because they have recently fixed some serious
bugs in it.
Let me know,
Joe -
DBMS_XMLSCHEMA.COPYEVOLVE failing with ORA-06502 ORA-30942 and ORA-30944
Hi all,
We have a procedure we're testing to evolve XML schemas. Fairly simple and straightforward, and on our development box (Win Server 2003) it works fine. However on our test server (Solaris) we get this -
tdm@TDMRSTG>Alter session set RECYCLEBIN=off
2 ;
Session altered.
Elapsed: 00:00:00.00
tdm@TDMRSTG>
1 begin
2 tdm_maintenance_pkg.EVOLVE_SCHEMA(
3 'http://uk-LONDBS006:8080/public/TDM/xsd/TDM_Computation_1_2_3.xsd',
4 'XMLDIR',
5 'evolveTDM_Computation_1.xsd'
6 );
7* end;
tdm@TDMRSTG>/
begin
ERROR at line 1:
ORA-30944: Error during rollback for XML schema 'http://uk-LONDBS006:8080/public/TDM/xsd/TDM_Computa
"TDM"."TDM_COMPUTATION" column 'XML'
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at "SYS.XMLTYPE", line 254
ORA-06512: at line 1
ORA-30942: XML Schema Evolution error for schema 'http://uk-LONDBS006:8080/public/TDM/xsd/TDM_Comput
"TDM"."TDM_COMPUTATION" column 'XML'
ORA-06502: PL/SQL: numeric or value error
ORA-06512: at "SYS.XMLTYPE", line 254
ORA-06512: at line 1
ORA-06512: at "XDB.DBMS_XMLSCHEMA_INT", line 113
ORA-06512: at "XDB.DBMS_XMLSCHEMA", line 210
ORA-06512: at "TDM.TDM_MAINTENANCE_PKG", line 47
ORA-06512: at line 2
Elapsed: 00:01:43.03
tdm@TDMRSTG>
Here's the listing of the procedure -
PROCEDURE evolve_schema ( p_oldSchema IN VARCHAR2
, p_directory IN VARCHAR2
, p_newSchema IN VARCHAR2 )
IS
BEGIN
DBMS_XMLSCHEMA.COPYEVOLVE(
xdb$string_list_t(p_oldSchema),
XMLSequenceType(xmltype(getXml(p_Directory,p_newSchema)) )
END;
We're all pretty new to all of this, so any help would be grately appreciated.
Regards
Geoff.Hello
You are selecting 8000 characters from position 4001, not 4000 characters from position 4001....
FUNCTION substr(lob_loc IN BLOB,
amount IN INTEGER := 32767,
offset IN INTEGER := 1)dbms_lob.substr(billing_inventory,4000,1),dbms_lob.substr(billing_inventory,8000,4001)
You need to modify the 2nd substr in each select statement to be
dbms_lob.substr(billing_inventory,4000,1),dbms_lob.substr(billing_inventory,4001,4000)
HTH
David
Edited by: David Tyler on Jun 27, 2011 1:16 PM -
Hi, guys!
Why in this PL/SQL code "COMMIT;" comand causes an error ORA-01002 ?
I use Microsift ODBC driver for Visual FoxPro.
DECLARE
TYPE EmpCurTyp IS REF CURSOR ;
emp_cv EmpCurTyp;
emp_new EmpCurTyp;
tab_name VARCHAR2(30);
D2 varchar(3);
BEGIN
OPEN emp_cv FOR 'select table_name T_N from [email protected]' ;
LOOP
FETCH emp_cv INTO tab_name;
EXIT WHEN emp_cv%NOTFOUND;
OPEN emp_new FOR 'select "ko" D2 from '| |tab_name| |'@ho.world ' ;
LOOP
FETCH emp_new INTO D2;
commit; -- << causes an error ORA-01002 fetch out of sequence
EXIT WHEN emp_new%NOTFOUND;
END LOOP;
ClOSE emp_new;
END LOOP;
CLOSE emp_cv;
END;
Thanks.
nullThanks for the suggestion
There are no "char(32767)"s in the package - altho there are "varchar2(32767)"s
I have tried a variotion on the script, outputting the result to a new table instead of updating the enrolment - which ran fine so the error is in the update.
I tried adding a step using the result in the temp table to update the enrolment table - and got my errors again. So there is something funny in my data. Nothing obvious shows.
The full temp table contains 745292 records - when it failed 150 records had been written.
I note that although I had expected only to find one record per enrolment, there are some where there are two (@#$%!! source system writing two "insert" audit records) - could my problem be that I am updating a record previously updated - where do I set the script to commit as it goes?
Sandra -
Bug and Fix: Report Template Preview displays ORA-01002
Hi, omniscient All!
Let me share some knowledge with you. There is an old APEX bug:
BUG: preview report template errors with ORA-01002
Report Template Preview/Copy Error
Template Preview Error:
You can definitely see it in 4.0, 4.1, 4.2, 4.2.1 versions: open any database application in AppBuilder, go to Shared Components→Templates, move cursor on Some Report Template row, click Preview Icon. Voilà:
report error:
ORA-01002: fetch out of sequenceI looked into Template Preview region's source and have found next WWV_RENDER_REPORT3.show call:
wwv_render_report3.show(
p_query => '
select 1 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual union
select 2 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual union
select 3 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual union
select 4 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual union
select 5 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual union
select 6 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual
order by 1',
p_row_template_id => :f4000_p245_id,
p_region_id => 88449328191587806
);I have no wish to go deep into my further investigation, therefore I just call a cause: APEX Team, you forgot to set the value of P_PLUG_SOURCE_TYPE parameter.
Workaround: While APEX Team will making a patch, those who can't wait it should fix it manually by executing next code:
update &APEX_SCHEMA.wwv_flow_page_plugs
set plug_source = q'{wwv_render_report3.show(
p_query => '
select 1 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual union
select 2 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual union
select 3 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual union
select 4 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual union
select 5 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual union
select 6 COL1, ''[...]'' COL2, ''[...]'' COL3, sysdate COL4 from dual
order by 1',
p_row_template_id => :f4000_p245_id,
p_region_id => 88449328191587806,
p_plug_source_type => 'SQL_QUERY'
where id = 14562627207747006
/APEX_SCHEMA is schema where APEX was installed.
Good luck,
Alex
Edited by: tiPPLer on 14.02.2013 17:14I wouldn't mind piggy-backing this to ask if the Report Template "shortcut" links at the top of the page can be updated to account for all sections that are now a part of the Report Template. "Before Each Row" and "After Each Row" sections are not listed in the shortcuts. There are also two shortcuts listed as "Before" and "After" which should probably be relabeled.
Shane. -
ORA-00604 and ORA-12899-- please explain...
ORA-00604: error occurred at recursive SQL level 1 ORA-12899: value too large for column "DVIR"."TB_USERS"."USER_DB_NAME" (actual: 12, maximum: 10) ORA-06512: at line 55 ORA-12899: value too large for column "DVIR"."TB_USERS"."USER_DB_NAME" (actual: 12, maximum: 10)
This error means you are trying to insert the value having 12 characters but the length of the column specified is 10. So you cannot insert the data beyond the specified limit. For Ex. you have specified varchar2(10) and the data you are inserting is more than 10 characters then you will get this error.
-
ORA-01401 and ORA-12899 : "too large for column" error messages
I posted this already in the Database - General forum.
Sorry for the double post.
For the past 8hours, I have been googling about
the related ORA-01401 and ORA-12899 error
messages.
I noticed that ORA-01401 had been removed from the list
of error messages in Oracle 10g documentation.
http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10744/e900.htm#sthref30
And, ORA-12899 has been added.
http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10744/e12700.htm
1. Is there an official Oracle document (e.g. release notes) stating such facts? If so, please provide the link.
2. Why did Oracle change the error code and not just update ORA-01401?
3. Someone posted in http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:7143933880166
Even if installed Oracle is 10g, when he tried to "insert a 100 into a number(2).",
he supposedly got ORA-01401. So, is ORA-01401 still part of 10g or not?
I have yet to confirm this myself.
Sorry for being meticulous. Our customer just wants to know the
information for the 2nd question. It's hard to convince them without
showing official documents.
Thanks!1)
Well, go to Metalink and check out Note 119119.1 (B.4) and Note:287754.1
2)
Such details are seldom published. One guess is what they changed altered the reason behind the message so using the same code would be a bad idea.
3)
If you are referring to the occurrence of ora-1401 from a select on a XE db, that may be a bug. -
For the past 8hours, I have been googling about
the related ORA-01401 and ORA-12899 error
messages.
I noticed that ORA-01401 had been removed from the list
of error messages since Oracle 10.1 documentation.
http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10744/e900.htm#sthref30
And, ORA-12899 has been added.
http://download-west.oracle.com/docs/cd/B14117_01/server.101/b10744/e12700.htm
Is there an official Oracle document (e.g. release notes)
stating such fact?Yes, there is : Documentation
But I have some doubt that Oracle Corp. will change anything else from the 10.1 documentation.
Furthermore, the doc is correct in regards of the database (error doc cannot differ of the database because this is a dump, so this is not a doco problem...) :
Connected to:
Oracle9i Enterprise Edition Release 9.2.0.4.0 - 64bit Production
With the Partitioning option
JServer Release 9.2.0.4.0 - Production
SQL> insert into notes_tbl (name) values ('too large value here');
insert into notes_tbl (name) values ('too large value here')
ERROR at line 1:
ORA-01401: inserted value too large for column
Connected to:
Oracle Database 10g Enterprise Edition Release 10.2.0.3.0 - Production
With the Partitioning, OLAP and Data Mining options
SQL> insert into notes_tbl (name) values ('too large value here');
insert into notes_tbl (name) values ('too large value here')
ERROR at line 1:
ORA-12899: value too large for column "SCOTT"."NOTES_TBL"."NAME" (actual: 20, maximum: 10)Nicolas. -
ORA-01002/ Fetch out of sequence on lazy loading
Hello,
We are facing an oracle SQLException (ORA-01002: fetch out of sequence)
while we are trying to get a field (retrieved via lazy loading) from an
object that was retrieved using a kodoquery.
This error only occurs during performance testing under a heavy load.
(100 concurrent users). For each thread we get a new persistencemanager
from the factory. And we have put the multithreaded option to true.
Can anyone help us with this problem?
Thanks in advance,
Kind Regards,
Niels Soeffers
Caused by: java.sql.SQLException: ORA-01002: fetch out of sequence
at
oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:112)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:331)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:288)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:743)
at
oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:216)
at
oracle.jdbc.driver.T4CPreparedStatement.fetch(T4CPreparedStatement.java:1027)
at
oracle.jdbc.driver.OracleResultSetImpl.close_or_fetch_from_next(OracleResultSetImpl.java:291)
at
oracle.jdbc.driver.OracleResultSetImpl.next(OracleResultSetImpl.java:213)
at
com.solarmetric.jdbc.DelegatingResultSet.next(DelegatingResultSet.java:97)
at kodo.jdbc.sql.ResultSetResult.nextInternal(ResultSetResult.java:151)
at kodo.jdbc.sql.AbstractResult.next(AbstractResult.java:123)
at kodo.jdbc.sql.Select$SelectResult.next(Select.java:2236)
at
kodo.jdbc.meta.AbstractCollectionFieldMapping.load(AbstractCollectionFieldMapping.java:592)
at kodo.jdbc.runtime.JDBCStoreManager.load(JDBCStoreManager.java:521)
at
kodo.runtime.DelegatingStoreManager.load(DelegatingStoreManager.java:133)
at kodo.runtime.ROPStoreManager.load(ROPStoreManager.java:79)
at kodo.runtime.StateManagerImpl.loadFields(StateManagerImpl.java:3166)
at kodo.runtime.StateManagerImpl.loadField(StateManagerImpl.java:3265)
at kodo.runtime.StateManagerImpl.isLoaded(StateManagerImpl.java:1386)
at
com.ardatis.ventouris.domain.OntvangstReeks.jdoGetontvangstTransacties(OntvangstReeks.java)
at
com.ardatis.ventouris.domain.OntvangstReeks.getStatus(OntvangstReeks.java:72)
at
com.ardatis.ventouris.service.financien.transfer.FinancienTOAssembler.getOntvangstReeksBaseTO(FinancienTOAssembler.java:71)
at
com.ardatis.ventouris.service.financien.transfer.FinancienTOAssembler.getOntvangstReeksBaseTOs(FinancienTOAssembler.java:84)
at
com.ardatis.ventouris.service.financien.FinancienManagerImpl.getOntvangstReeksBaseTOs(FinancienManagerImpl.java:241)
at
com.ardatis.ventouris.service.financien.ejb.FinancienManagerBean.getOntvangstReeksBaseTOs(FinancienManagerBean.java:62)
at sun.reflect.GeneratedMethodAccessor181.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at com.sun.enterprise.security.SecurityUtil$2.run(SecurityUtil.java:153)
at java.security.AccessController.doPrivileged(Native Method)
at
com.sun.enterprise.security.application.EJBSecurityManager.doAsPrivileged(EJBSecurityManager.java:950)
at com.sun.enterprise.security.SecurityUtil.invoke(SecurityUtil.java:158)
at
com.sun.ejb.containers.EJBObjectInvocationHandler.invoke(EJBObjectInvocationHandler.java:128)
at $Proxy31.getOntvangstReeksBaseTOs(Unknown Source)
at sun.reflect.GeneratedMethodAccessor155.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
com.sun.corba.ee.impl.presentation.rmi.ReflectiveTie._invoke(ReflectiveTie.java:123)We are using Oracle 10g and have tried multiple dirvers. (classes12.jar,
ojdbc14.jar)
Our kodo.properties ( actually the ra.xml we supply with the kodo.rar )
<connector>
<display-name>KodoJDO</display-name>
<description>Resource Adapter for integration of the Kodo Java Data
Objects (JDO) implementation with J2EE 1.3 compliant managed
environments</description>
<vendor-name>Solarmetric, Inc.</vendor-name>
<spec-version>1.0</spec-version>
<eis-type>jdo</eis-type>
<version>1.0</version>
<license>
<description>
See http://www.solarmetric.com for terms and license conditions.
</description>
<license-required>true</license-required>
</license>
<resourceadapter>
<managedconnectionfactory-class>kodo.jdbc.ee.JDBCManagedConnectionFactory</managedconnectionfactory-class>
<connectionfactory-interface>javax.resource.cci.ConnectionFactory</connectionfactory-interface>
<connectionfactory-impl-class>kodo.jdbc.ee.JDBCConnectionFactory</connectionfactory-impl-class>
<connection-interface>javax.resource.cci.Connection</connection-interface>
<connection-impl-class>kodo.runtime.PersistenceManagerImpl</connection-impl-class>
<transaction-support>XATransaction</transaction-support>
<config-property>
<description>A comma-separated list of query aggregate listeners
to add to the default list of extensions. Each listener must implement
the kodo.jdbc.query.JDBCAggregateListener interface.</description>
<config-property-name>AggregateListeners</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The kodo.jdbc.meta.ClassIndicator to use by default
for new mappings. The class indicator is responsible for tracking the
concrete class or subclass implemented by the object stored in each row of
a table.</description>
<config-property-name>ClassIndicator</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>in-class-name</config-property-value>
</config-property>
<config-property>
<description>The kodo.util.ClassResolver implementation that
should be used for JDO class resolution. Defaults to a JDO spec-compliant
resolver.</description>
<config-property-name>ClassResolver</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>spec</config-property-value>
</config-property>
<config-property>
<description>Details about various compatibiity levels for the
current environment.</description>
<config-property-name>Compatibility</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>true</config-property-value>
</config-property>
<config-property>
<description>The class name of either the JDBC java.sql.Driver, or
an instance of a javax.sql.DataSource to use to connect to the non-XA data
source.</description>
<config-property-name>Connection2DriverName</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The password for the user specified in
Connection2UserName</description>
<config-property-name>Connection2Password</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>A comma-separated list of properties to be passed to
the non-XA JDBC Driver when obtaining a Connection. Properties are of the
form "key=value". If the given JDBC Driver class is a DataSource, these
properties will be used to configure the bean properties of the
DataSource. </description>
<config-property-name>Connection2Properties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The URL for the non-XA data source.</description>
<config-property-name>Connection2URL</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The username for the connection listed in
Connection2URL.</description>
<config-property-name>Connection2UserName</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>A comma-separated list of
com.solarmetric.jdbc.ConnectionDecorator implementations to install on all
connection pools.</description>
<config-property-name>ConnectionDecorators</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The class name of either the JDBC java.sql.Driver, or
an instance of a javax.sql.DataSource to use to connect to the data
source.</description>
<config-property-name>ConnectionDriverName</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The JNDI name of the connection factory to use for
finding non-XA connections. If specified, this is the connection that
will be used for obtaining sequence numbers.</description>
<config-property-name>ConnectionFactory2Name</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>jdbc/VentourisNonXA</config-property-value>
</config-property>
<config-property>
<description>A comma-separated list of properties used to
configure the javax.sql.DataSource used as the non-XA ConnectionFactory.
Each property should be of the form "key=value", where "key" is the name
of some bean-like property of the data source.</description>
<config-property-name>ConnectionFactory2Properties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The JNDI name of the connection factory to use for
obtaining connections.</description>
<config-property-name>ConnectionFactoryName</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>jdbc/Ventouris</config-property-value>
</config-property>
<config-property>
<description>A comma-separated list of properties used to
configure the javax.sql.DataSource used as the ConnectionFactory. Each
property should be of the form "key=value", where "key" is the name of
some bean-like property of the data source.</description>
<config-property-name>ConnectionFactoryProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The password for the user specified in
ConnectionUserName</description>
<config-property-name>ConnectionPassword</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>A comma-separated list of properties to be passed to
the JDBC Driver when obtaining a Connection. Properties are of the form
"key=value". If the given JDBC Driver class is a DataSource, these
properties will be used to configure the bean properties of the
DataSource. </description>
<config-property-name>ConnectionProperties</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>This property dictates when PersistenceManagers will
retain and release data store connections. Available options are
"on-demand" for retaining a connection only during pessimistic
transactions and data store operations, "transaction" for retaining a
connection for the life of each transaction, or "persistence-manager" to
indicate that a persistence manager should retain and reuse a single
connection for its entire lifespan.</description>
<config-property-name>ConnectionRetainMode</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>transaction</config-property-value>
</config-property>
<config-property>
<description>The URL for the data source.</description>
<config-property-name>ConnectionURL</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The username for the connection listed in
ConnectionURL.</description>
<config-property-name>ConnectionUserName</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>Set to true if you''d like Kodo to copy all object
ids before returning them to your code. If you do not plan on modifying
identity objects, you can set this property to false to avoid the copying
overhead.</description>
<config-property-name>CopyObjectIds</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>false</config-property-value>
</config-property>
<config-property>
<description>Plugin used to cache data loaded from the data store.
Must implement kodo.datacache.DataCache.</description>
<config-property-name>DataCache</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The number of milliseconds that data in the data
cache is valid for. A value of 0 or less means that by default, cached
data does not time out.</description>
<config-property-name>DataCacheTimeout</config-property-name>
<config-property-type>java.lang.Integer</config-property-type>
<config-property-value>-1</config-property-value>
</config-property>
<config-property>
<description>The type of data source in use. Available options
are "local" for a standard data source under Kodo''s control, or
"enlisted" for a data source managed by an application server and
automatically enlisted in global transactions.</description>
<config-property-name>DataSourceMode</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>enlisted</config-property-value>
</config-property>
<config-property>
<description>The kodo.jdbc.sql.DBDictionary to use for database
interaction. This is auto-detected based on the setting of
javax.jdo.option.ConnectionURL, so you need only set this to override the
default with your own custom dictionary or if you are using an
unrecognized driver.</description>
<config-property-name>DBDictionary</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>Whether to dynamically create custom structs to hold
and transfer persistent state in the Kodo data cache and remote
persistence manager frameworks. Dynamic structs can reduce data cache
memory consumption, reduce the amount of data serialized back and forth
under remote persistence managers, and improve the overall performance of
these systems. However, they increase application warm-up time while the
custom classes are generated and loaded into the JVM. Set to true to
enable dynamic data structs.</description>
<config-property-name>DynamicDataStructs</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>false</config-property-value>
</config-property>
<config-property>
<description>Specifies the default eager fetch mode to use.
Either "none" to never eagerly-load relations, "join" for selecting 1-1
relations along with the target object using inner or outer joins, or
"parallel" for selecting 1-1 relations via joins, and collections
(including to-many relations) along with the target object using separate
select statements executed in parallel.</description>
<config-property-name>EagerFetchMode</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>parallel</config-property-value>
</config-property>
<config-property>
<description>The number of rows that will be pre-fetched when an
element in a Query result is accessed. Use -1 to pre-fetch all
results.</description>
<config-property-name>FetchBatchSize</config-property-name>
<config-property-type>java.lang.Integer</config-property-type>
<config-property-value>-1</config-property-value>
</config-property>
<config-property>
<description>The name of the JDBC fetch direction to use.
Standard values are "forward", "reverse", and "unknown".</description>
<config-property-name>FetchDirection</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>forward</config-property-value>
</config-property>
<config-property>
<description>A comma-separated list of fetch group names that
PersistenceManagers will load by default when loading data from the data
store.</description>
<config-property-name>FetchGroups</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>A comma-separated list of query filter listeners to
add to the default list of extensions. Each listener must implement the
kodo.jdbc.query.JDBCFilterListener interface.</description>
<config-property-name>FilterListeners</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>Whether or not Kodo should automatically flush
modifications to the data store before executing queries.</description>
<config-property-name>FlushBeforeQueries</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>with-connection</config-property-value>
</config-property>
<config-property>
<description>If true, Kodo will order all SQL inserts, updates,
and deletes to meet your schema''s foreign key constraints. Defaults to
false.</description>
<config-property-name>ForeignKeyConstraints</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>false</config-property-value>
</config-property>
<config-property>
<description>If false, then the JDO implementation must consider
modifications, deletions, and additions in the PersistenceManager
transaction cache when executing a query inside a transaction. Else, the
implementation is free to ignore the cache and execute the query directly
against the data store.</description>
<config-property-name>IgnoreCache</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>true</config-property-value>
</config-property>
<config-property>
<description>Plugin used to manage inverse relations during flush.
Set to true to use the default inverse manager. Custom inverse managers
must extend kodo.runtime.InverseManager.</description>
<config-property-name>InverseManager</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>false</config-property-value>
</config-property>
<config-property>
<description>A comma-separated list of
com.solarmetric.jdbc.JDBCListener implementations to install on all
connection pools.</description>
<config-property-name>JDBCListeners</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>The license key provided to you by SolarMetric. Keys
are available at www.solarmetric.com</description>
<config-property-name>LicenseKey</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value><KEY-REMOVED></config-property-value>
</config-property>
<config-property>
<description>Plugin used to handle acquiring locks on persistent
instances. Must implement kodo.runtime.LockManager.</description>
<config-property-name>LockManager</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>pessimistic</config-property-value>
</config-property>
<config-property>
<description>The number of milliseconds to wait for an object lock
before throwing an exception, or -1 for no limit.</description>
<config-property-name>LockTimeout</config-property-name>
<config-property-type>java.lang.Integer</config-property-type>
<config-property-value>-1</config-property-value>
</config-property>
<config-property>
<description>LogFactory and configuration for Kodo''s logging
needs.</description>
<config-property-name>Log</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>kodo(DefaultLevel=WARN, Tool=WARN,
Runtime=WARN, SQL=WARN)</config-property-value>
</config-property>
<config-property>
<description>The mode to use for calculating the size of large
result sets. Legal values are "unknown", "last", and "query".</description>
<config-property-name>LRSSize</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>query</config-property-value>
</config-property>
<config-property>
<description>Plugin used to integrate with an external transaction
manager. Must implement kodo.runtime.ManagedRuntime.</description>
<config-property-name>ManagedRuntime</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>auto</config-property-value>
</config-property>
<config-property>
<description>Plugin used to configure management and profiling
capabilities.</description>
<config-property-name>ManagementConfiguration</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>none</config-property-value>
</config-property>
<config-property>
<description>The kodo.jdbc.meta.MappingFactory that will provide
the object-relational mapping information needed to map each persistent
class to the database.</description>
<config-property-name>MappingFactory</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>file</config-property-value>
</config-property>
<config-property>
<description>Plugin used to create metadata about persistent
types. Must implement kodo.meta.MetaDataLoader</description>
<config-property-name>MetaDataLoader</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>jdo</config-property-value>
</config-property>
<config-property>
<description>If true, then the application plans to have multiple
threads simultaneously accessing a single PersistenceManager, so measures
must be taken to ensure that the implementation is thread-safe. Otherwise,
the implementation need not address thread safety.</description>
<config-property-name>Multithreaded</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>true</config-property-value>
</config-property>
<config-property>
<description>If true, then it is possible to read persistent data
outside the context of a transaction. Otherwise, a transaction must be in
progress in order read data.</description>
<config-property-name>NontransactionalRead</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>true</config-property-value>
</config-property>
<config-property>
<description>If true, then it is possible to write to fields of a
persistent-nontransactional object when a transaction is not in progress.
If false, such a write will result in a JDOUserException.</description>
<config-property-name>NontransactionalWrite</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>false</config-property-value>
</config-property>
<config-property>
<description>Determines the persistence manager's behavior in
calls to getObjectById with a validate parameter of false. Use "check" to
check that a database record exists for the object and load its fetch
group fields. Use "hollow" to return a hollow instance.</description>
<config-property-name>ObjectLookupMode</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>check</config-property-value>
</config-property>
<config-property>
<description>Selects between optimistic and pessimistic (data
store) transactional modes.</description>
<config-property-name>Optimistic</config-property-name>
<config-property-type>java.lang.Boolean</config-property-type>
<config-property-value>true</config-property-value>
</config-property>
<config-property>
<description>Action to take when Kodo discovers an orphaned key in
the database. May be a custom action implementing
kodo.event.OrphanedKeyAction.</description>
<config-property-name>OrphanedKeyAction</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>log</config-property-value>
</config-property>
<config-property>
<description>The name of the concrete implementation of
javax.jdo.PersistenceManagerFactory that
javax.jdo.JDOHelper.getPersistenceManagerFactory () should create. For
Kodo JDO, this should be kodo.jdbc.runtime.JDBCPersistenceManagerFactory
or a custom extension of this type.</description>
<config-property-name>PersistenceManagerFactoryClass</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>kodo.jdbc.runtime.JDBCPersistenceManagerFactory</config-property-value>
</config-property>
<config-property>
<description>Persistence manager plugin and properties. If you
use a custom class, it must extend
kodo.runtime.PersistenceManagerImpl.</description>
<config-property-name>PersistenceManagerImpl</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>default</config-property-value>
</config-property>
<config-property>
<description>Configure this persistence manager factory to service
remote persistence managers.</description>
<config-property-name>PersistenceManagerServer</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>false</config-property-value>
</config-property>
<config-property>
<description>A comma-separated list of the class names of all
persistent classes to register whenever a persistence manager is
obtained.</description>
<config-property-name>PersistentClasses</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>com.ardatis.ventouris.domain.KwartaalVerhoging,
com.ardatis.ventouris.domain.Land, com.ardatis.ventouris.domain.Gemeente,
com.ardatis.ventouris.domain.Adres,
com.ardatis.ventouris.domain.ContactGegeven,
com.ardatis.ventouris.domain.AdresContactGegeven,
com.ardatis.ventouris.common.type.AdresType,
com.ardatis.ventouris.domain.OntvangstTransactie,
com.ardatis.ventouris.domain.OntvangstReeks,
com.ardatis.ventouris.domain.Ontvangst,
com.ardatis.ventouris.domain.Inkomen,
com.ardatis.ventouris.domain.loopbaan.LoopbaanPeriode,
com.ardatis.ventouris.common.type.InkomenSoort,
com.ardatis.ventouris.common.type.INSZ,
com.ardatis.ventouris.domain.Aangeslotene,
com.ardatis.ventouris.domain.NatuurlijkePersoon,
com.ardatis.ventouris.domain.Persoon, com.ardatis.ventouris.domain.Rol,
com.ardatis.ventouris.domain.Dossier,
com.ardatis.ventouris.common.type.Geslacht,
com.ardatis.ventouris.common.type.Taal,
com.ardatis.ventouris.common.type.Nationaliteit,
com.ardatis.ventouris.common.type.KostType,
com.ardatis.ventouris.domain.Verhoging,
com.ardatis.ventouris.domain.Aanvraag,
com.ardatis.ventouris.domain.AanvraagAansluitingSS,
com.ardatis.ventouris.domain.AanvraagToestand,
com.ardatis.ventouris.common.type.AanvraagToestandType,
com.ardatis.ventouris.domain.Factuur,
com.ardatis.ventouris.domain.TaakType, com.ardatis.ventouris.domain.Taak,
com.ardatis.ventouris.domain.BijdrageBerekening,
com.ardatis.ventouris.domain.calculationparameters.HerwaarderingsIndex,
com.ardatis.ventouris.domain.integration.asis.TempInterneOntvangst,
com.ardatis.ventouris.domain.calculationparameters.InkomenGrens,
com.ardatis.ventouris.domain.calculationparameters.BijdrageCategorie,
com.ardatis.ventouris.domain.calculationparameters.BijdrageCategorieGroep,
com.ardatis.ventouris.domain.integration.asis.TempOntvangstKinderbijslag,
com.ardatis.ventouris.domain.calculationparameters.JaarVerhogingParameter,
com.ardatis.ventouris.domain.calculationparameters.KwartaalVerhogingParameter,
com.ardatis.ventouris.domain.UitgaveReeks,
com.ardatis.ventouris.domain.Uitgave,
com.ardatis.ventouris.domain.Terugbetaling,
com.ardatis.ventouris.domain.BedragTerugbetaald,
com.ardatis.ventouris.domain.BijdrageSS</config-property-value>
</config-property>
<config-property>
<description>Plugin used to proxy second class object fields of
managed instances. Must implement kodo.util.ProxyManager.</description>
<config-property-name>ProxyManager</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>default</config-property-value>
</config-property>
<config-property>
<description>Plugin used to cache query results loaded from the
data store. Must implement kodo.datacache.QueryCache.</description>
<config-property-name>QueryCache</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>true</config-property-value>
</config-property>
<config-property>
<description>Plugin used to cache query compilation data. Must
implement java.util.Map. Does not need to be thread-safe -- it will be
wrapped via the Collections.synchronizedMap() method if it does not extend
kodo.util.CacheMap.</description>
<config-property-name>QueryCompilationCache</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>true</config-property-value>
</config-property>
<config-property>
<description>The default lock level to use when loading objects
within non-optimistic transactions. Set to none, read, write, or the
numeric value of the desired lock level for your lock
manager.</description>
<config-property-name>ReadLockLevel</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value>read</config-property-value>
</config-property>
<config-property>
<description>Plugin used to communicate commit information among
JVMs. Must implement kodo.event.RemoteCommitProvider.</description>
<config-property-name>RemoteCommitProvider</config-property-name>
<config-property-type>java.lang.String</config-property-type>
<config-property-value></config-property-value>
</config-property>
<config-property>
<description>Whether or not RemoteCommitEvents will include the
object Ids of objects added during the transaction.</description>
<config-property-name>RemoteCommitTransmitAddObjectIds</config-property-na -
ERROR ORA-01002 ??????
Hi! sorry by my English......
I have this Package:
CREATE OR REPLACE PACKAGE PCK_KK
AS
TYPE CURBATCH IS REF CURSOR;
PROCEDURE PROC_SUBKK
BATCH_SEG OUT CURBATCH,
BATCH_PES OUT CURBATCH,
NUMERROR$ OUT NUMBER,
MSJERROR$ OUT VARCHAR2
END PCK_KK;
CREATE OR REPLACE PACKAGE BODY PCK_KK
AS
PROCEDURE PROC_SUBKK
BATCH_SEG OUT CURBATCH,
BATCH_PES OUT CURBATCH,
NUMERROR$ OUT NUMBER,
MSJERROR$ OUT VARCHAR2
IS
BEGIN
BEGIN
OPEN BATCH_SEG FOR
SELECT
CODIGO_SEG,
NOMBRE_SEG
FROM
PESQUERIAS.SEGUIMIENTO@TI_PESQUERIA.US.ORACLE.COM
ORDER BY
NOMBRE_SEG;
OPEN BATCH_PES FOR
SELECT
SEGUIMIENTO.CODIGO_SEG,
PESQUERIA.COD_PESQUERIA,
PESQUERIA.NOMBRE_PESQUERIA
FROM
PESQUERIAS.PESQUERIA@TI_PESQUERIA.US.ORACLE.COM INNER JOIN
(PESQUERIAS.SEGUIMIENTO@TI_PESQUERIA.US.ORACLE.COM INNER JOIN
PESQUERIAS.SEGUIMIENTO_PESQUERIA@TI_PESQUERIA.US.ORACLE.COM
ON SEGUIMIENTO.CODIGO_SEG = SEGUIMIENTO_PESQUERIA.COD_SEG)
ON PESQUERIA.COD_PESQUERIA = SEGUIMIENTO_PESQUERIA.COD_PES
ORDER BY
SEGUIMIENTO.CODIGO_SEG,
PESQUERIA.COD_PESQUERIA;
NUMERROR$ := 0;
MSJERROR$ := '';
RETURN;
EXCEPTION
WHEN OTHERS THEN
NUMERROR$ := SQLCODE;
CASE NUMERROR$
WHEN 100 THEN MSJERROR$:='bla bla bla';
WHEN -1 THEN MSJERROR$:='other bal bla bla';
ELSE MSJERROR$:= 'ERROR [PCK_KK] '||to_char(SQLERRM);
END CASE;
END;
END PROC_SUBKK;
END PCK_KK;
Ok, I execute by SqlPlus and ok!!!!!
but, by PHP so:
Warning: ocifetchstatement(): OCIFetchStatement:
ORA-01002: recuperación fuera de secuencia
in /ifop/ti/P_center_ingresar.php on line 72
And my source php is:
$Coneccion = OCILogon($User, $Passwd, $HostOracle);
$Cursor = OCINewCursor($Coneccion);
$sTmpSql = OCIParse($Coneccion,"BEGIN PROC_SUBKK.PCK_KK(:rTmp1,:rTmp2,:lNumError,:sMsjError); END;");
OCIBindByName($sTmpSql,":rTmp1",&$Cursor,-1,OCI_B_CURSOR);
OCIBindByName($sTmpSql,":rTmp2",&$Cursor,-1,OCI_B_CURSOR);
OCIBindByName($sTmpSql,":lNumError",&$lNumError,32);
OCIBindByName($sTmpSql,":sMsjError",&$sMsjError,32);
ociexecute($sTmpSql);
ociexecute($Cursor);
if ($lNumError == 0)
$rTmp1_RecordCount = OCIfetchstatement($Cursor,&$rTmp1);
if ($rTmp1_RecordCount > 0)
for ($lTmp1 = 0; $lTmp1 < $rTmp1_RecordCount; $lTmp1++ )
$aTmp1[$lTmp1][1] = $rTmp1["CODIGO_SEG"][$lTmp1];
$aTmp1[$lTmp1][2] = $rTmp1["NOMBRE_SEG"][$lTmp1];
$rTmp2_RecordCount = OCIfetchstatement($Cursor,&$rTmp2); <--- ERROR!!!!!! ??????
if ($rTmp2_RecordCount > 0)
//Si viene registros, traspasa a arreglo
for ($lTmp1 = 0; $lTmp1 < $rTmp2_RecordCount; $lTmp1++ )
$aTmp2[$lTmp1][1] = $rTmp1["CODIGO_SEG"][$lTmp1];
$aTmp2[$lTmp1][2] = $rTmp1["COD_PESQUERIA"][$lTmp1];
$aTmp2[$lTmp1][3] = $rTmp1["NOMBRE_PESQUERIA"][$lTmp1];
OCIFreeStatement($sTmpSql);
OCIFreeCursor($Cursor);
OCILogoff($Coneccion);
else
OCIFreeStatement($sTmpSql);
OCIFreeCursor($Cursor);
OCILogoff($Coneccion);
HELPME PLEASE
THANKS !!!!
My configuration !!!!
Web Server//
RedHat Advanced Server 2.1
Oracle Application Server 10g
Php 5
DB Server//
RedHat Advanced Server 2.1
Oracle 9i
THANKS AGAIN !!!!Dear CJJ:
I proved subject "$cursor1 and $cursor2, for the two ref cursor parameters" and I work myself perfectly...thank you very much !!!!
$Cursor1 = OCINewCursor($Coneccion);
$Cursor2 = OCINewCursor($Coneccion);
$sTmpSql = OCIParse($Coneccion,"BEGIN TI_SEL001SEGUIMIENTOPESQUERIA.SEL001SEGUIMIENTOPESQUERIA(:rTmp1,:rTmp2,:lNumError,:sMsjError); END;");
OCIBindByName($sTmpSql,":rTmp1",&$Cursor1,-1,OCI_B_CURSOR);
OCIBindByName($sTmpSql,":rTmp2",&$Cursor2,-1,OCI_B_CURSOR);
OCIBindByName($sTmpSql,":lNumError",&$lNumError,32);
OCIBindByName($sTmpSql,":sMsjError",&$sMsjError,32);
ociexecute($sTmpSql);
ociexecute($Cursor1);
ociexecute($Cursor2);
I work without problems
THANKS !!!!!! -
ORA-01002-Error in Select ... for update
I would like to insert CLOB in a table (VP_EVENTS) with a primary key (eventid) with the following code:
String content = "AAAAAAAAAAAAABBBBBBBBBBXXX";
PreparedStatement cs = this.con.prepareStatement("INSERT INTO vp_events (eventid,term,participant)
VALUES (?,?,empty_clob())");
//Register IN-Parameter
cs.setInt(1, 1);
cs.setInt(2, 1);
cs.setTimestamp(3, new java.sql.Timestamp( System.currentTimeMillis() ));
//Execute statement
cs.execute();
cs.close();
Statement stmt = con.createStatement();
ResultSet clobLocatorSet = stmt.executeQuery( "SELECT PARTICIPANT FROM VP_EVENTS WHERE EVENTID=1 FOR UPDATE");
// Get the CLOB-locator
if (clobLocatorSet.next())
oracle.sql.CLOB clob =
((oracle.jdbc.driver.OracleResultSet)
clobLocatorSet).getCLOB(1);
// Write CLOB-Data
// The first parameter to plsql_write, is // the offset from which to start
// writing, and the second parameter is the // data to be written.
// plsql_length(), returns the length of // the data in the CLOB column
countCLOB = clob.plsql_write(
0,content.toCharArray());
At the execution-point of the "Select for Update"-statement the oracle thin driver throws the Error "Fetch out of sequence ORA-01002".
What's wrong?Connection conn = DriverManager.getConnection ("jdbc racle:thin:@myhost:1521:ORCL","scott", "tiger");
conn.setAutoCommit(false);
Statement stmt = conn.createStatement ();
null
Maybe you are looking for
-
Problem in making installation package by adobe air sdk
I made an installation file with adobe air (a javascript/html code by installing AIRSDK) , after makeing the file when I want to run it , it send an error message "This application cannot be installed because this installer has been mis-configured.
-
Change from 10.4.11 to 10.5...
Hi there, I'm using OS X 10.4.11 togethet with Logic Pro 8 and want to change to Leopard 10.5. Is there conflicts concerning Logic Pro 8? Will I have to reinstall Logic Pro 8? Thank for your help!
-
HORRIFIC Customer Service and Dishonest Business Practices
After well over a decade of service with Verizon Wireless and having 6 active lines with them, Verizon has not only lost my business, I will do everything within my power to convince everyone I know or ever come in contact with that Verizon is not a
-
How to change a item's color programmatically?
I want to change a item'color,(old background_color white,change it to gray)in a plsql program,is there any help from u all?
-
I am trying to speed up my video clip in imovie 09 but it doesnt give me the option to change the speed on my video adjustments clip tab..Help me please..