ORA-00976: virtual specified or operator not allowed here - (11g)
This ora error occurs on one of my test environment.ORA-00976: virtual specified or operator not allowed here
This happens in one of the plsql pkg, which has no compilation errors. and works perfectly well in other environments.
The only difference I noticed is what error in DB, which is 11g - 11.2.0.3
and other environments that are in good shape is 10g - 10.2.0.5
Overall of the function where the error is, there is one thing which I suspect (but not sure)
It is CONNECT BY LEVEL, is used in a query. This could be a problem in 11g?
If not, any help / troubleshooting tips that will be greatly appreciated. !
-Thank you,
I can reproduce your error on my 11.2.0.3 instance. Looks like the bug number 13496250 introduced in the 11.2.0.3.
John
Tags: Database
Similar Questions
-
ORA-00976: virtual specified or operator not allowed here
Hello
We had error after upgrade of GR 11, 2, in the insert statement.
INSERT INTO SDE_TBL_FLEXTRIMSITROUT
(BRANCHCD,
SOURCECD,
CURRENTNO,
BATCHNO,
DEPTCD,
CTL
INITIATIONDATE,
AMOUNT,
ACCOUNT,
ACCOUNTBRANCH,
TXNCD,
DEBITCREDIT,
LCYEQUIVALENT,
EXCHRATE,
VALUEDATE,
INSTRUMENTNO,
RELCUST,
ADDLTEXT,
TXNMIS1,
TXNMIS2,
TXNMIS3,
TXNMIS4,
TXNMIS5,
TXNMIS6,
TXNMIS7,
TXNMIS8,
TXNMIS9,
TXNMIS10,
COMPMIS1,
COMPMIS2,
COMPMIS3,
COMPMIS4,
COMPMIS5,
COMPMIS6,
COMPMIS7,
COMPMIS8,
COMPMIS9,
COMPMIS10,
COSTCODE1,
COSTCODE2,
COSTCODE3,
COSTCODE4,
COSTCODE5,
RELATEDACCOUNT,
RELATEDREF,
USERREFERENCE,
ACCTPOSTOVERWRITE,
EXCHRATEOVERWRITE,
VALUEDATEOVERWRITE,
ACCTBALOVERWRITE,
ITRREFER,
RefinanceAmount,
PROCESSID)
VALUES
(vBranchCode,
cCreateNewTrimsITR_rec. APPLSYS,
ROWNUM,
nBatchNo,
cCreateNewTrimsITR_rec. DEPT,
vCcy,
To_date (cCreateNewTrimsITR_rec. HOUR, 'YYYYMMDD'),
nAmount,
vAccount,
vAccountBranch, - added by Sibylle
vTxnCd,
cDebitCredit,
nLcyEquivalent,
nExchRate,
To_date (cCreateNewTrimsITR_rec. VALUEDATE, 'YYYYMMDD'),
vInstrumentNo,
--' ' || SUBSTR (cCreateNewTrimsITR_rec. ITRREFER, 2, 11),
vFlxCntry | cCreateNewTrimsITR_rec. APNO,
vDesc,
cCreateNewTrimsITR_rec. TRANSOUC,
RPAD (' ', 9);
vExpenseMIS,
vProductMIS,
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 9);
RPAD (' ', 20);
cCreateNewTrimsITR_rec. THEIRREF,
RPAD (' ', 16).
cActPostOverwrite,
cExchRateOverWrite,
cValueDateOverWrite,
cAcctBalOverWrite,
cCreateNewTrimsITR_rec. ITRREFER,
cCreateNewTrimsITR_rec. REFIAMOUNT,
nFlexOutProcessId);
Error: ORA-00976: specified virtual or operator not allowed here
According to the audit, which are a problem in GR 11, 2 with insert query using rownum in values.
Someone knows how to fix this?
I wonder why you want to use rownum as a value of insertion? It's not really worth doing an insert without a select statement.
If you want to use it, it would look like
Insert into t1 (name, row_num_value)
Select name
rownum
the t2;
But then you can use an order by clause, on the other it would spoil the rownum order. So an important question is, where is the rownum used for?
-
ORA-00976 LEVEL, PRIOR or ROWNUM not allowed here in the PO_DOCUMENT_CH package
Hello
EBS R12.1
OEL 5.4
Operations of requisition and PO doing im but I got error
Note > ORA-00976 error while approving internal requisitions [968651.1 ID]ORA-00976 LEVEL,PRIOR, or ROWNUM not allowed here in Package PO_DOCUMENT_CHECKS_PVT Procedure CHECK_REQUISITIONS. Solution 1. Please check HR Locations setup corresponding to location_id=XXX. For example the Country should be 'KE' instead of 'Kenya'. Compare with that of location_id=YYY which is correct as per FND log. select location_id,location_code,country from hr_locations_all where location_id in (142,182); 2. After changing above setup, please run the SQL again to confirm the value.
is the same thing with my mistake. But it is specific to the country in KENYA. :(
How can I get my FND journal so that I can see what location_id who got the error?
1* select location_id,location_code,country from hr_locations_all SQL> / LOCATION_ID LOCATION_CODE COUNTRY ----------- ------------- -------- censored Im selecting the table but it seems the location and country code are fine. Please help me resolve this one based on the notes above. Thanks a lot, Ms K Edited by: user_unlimited on Sep 16, 2010 10:28 PM
Salvation;
Please update thread when you did at the end of reading
Respect of
HELIOS -
Hello!!
I use jdeveloper 11.1.1.5
I am trying to do this in the AMImpl method
I get an error message like operation not permitted heregapbr.setAttribute("GapbDebitAmt",(gapbr.getAttribute("GapbDebitAmt")+ghlr.getAttribute("GjlDebitAmt")))
Have you read the docs? Do you know what it returns getAttribute (). It returns an object. Can add you a table and a Chair? Convert them to open the types then add
-
ORA-01719: outer join operator (+) not allowed in operand of GOLD or IN
I'm migrating a stored procedure (package) in Oracle 11 g. The SQL has an outer join, combined with a "GOLD":
Select a.row1, a.row2, b.row3, b.row4, c.row5, c.row6
schema1.table1 a, schema1.table2 b, schema2.table3 c
where
((c.orgunit = a.org (+) and b.newaccount (+) and TO_CHAR(c.createdatetime,'MM/DD/YYYY = c.account and c.feed = 'FOO' ') = TO_CHAR (SYSDATE, ' DD/MM/YYYY'))
or
((c.feed = 'BAR' and c.orgunit = a.org (+) and c.account b.newaccount (+) and TO_CHAR(c.createdatetime,'MM/DD/YYYY =') = TO_CHAR (SYSDATE, ' DD/MM/YYYY'));
The error is:
ORA-01719: outer join operator not allowed in operand of GOLD or IN
* Cause: Outer join appears in a clause or.
* Action: If A and B are predicates, to achieve the effect of (has or B).
I do not understand how to apply the suggested action to my query above. Can anyone provide a solution or a workaround?
Thank you.
your base table is c, a and b must be attached to the left
Select a.row1, a.row2, b.row3, b.row4, c.row5, c.row6
of schema2.table3 c
Join schema1.table1 left a c.orgunit on = a.org
c.account left join schema1.table2 b = b.newaccount
where c.createdatetime > = trunc (sysdate)
and c.createdatetime<>
and (c.feed = 'FOO' or c.feed = 'BAR');
-
ORA-01733-virtual column not allowed here - insert using inline view
Does anyone know why I get ORA-01733-virtual column not allowed here
SQL > select * from v version $;
BANNER
--------------------------------------------------------------------------------
Oracle Database 11g Enterprise Edition Release 11.1.0.6.0 - Production
PL/SQL release 11.1.0.6.0 - Production
CORE 11.1.0.6.0 Production
AMT for 32-bit Windows: Version 11.1.0.6.0 - Production
NLSRTL Version 11.1.0.6.0 - Production
-no error without the WITH CHECK option
SQL > INSERT INTO
2 (SELECT
3 location_id,
4 city
5 l.country_id
6 OF country c, localities, regions r l
7 where l.country_id = c.country_id
8 and c.region_id = r.region_id
9 and r.region_name = 'Asia')
10 VALUES (5500, 'Common Wansdworth', 'UK');
1 line of creation.
SQL > rollback;
Complete restoration.
-error with WITH CHECK OPTION
SQL > INSERT INTO
2 (SELECT
3 location_id,
4 city
5 l.country_id
6 OF country c, localities, regions r l
7 where l.country_id = c.country_id
8 and c.region_id = r.region_id
9 and r.region_name = 'Asia' WITH CHECK OPTION)
10 VALUES (5500, 'Common Wansdworth', 'UK');
INSERT INTO
*
ERROR on line 1:
ORA-01733: virtual column not allowed here
I was expecting
ORA-01402: discovers the violation of where WITH CHECK OPTION clause
for the second. Am I missing here?Coskan wrote:
RandolfThanks a lot for the update of this old question
After reading the link, I think I should ignore this error and accept him as ORA-01402The information that you have asked me to check me do not have an understanding of the different error types.
Coskan,
I didn't know this is an old thread that somehow got updated by someone else.
Regarding your question: you're right that the output of the script is not really that useful.
I have just run on 10.2.0.4 and in general, it seems that the output of USER_UPDATABLE_COLUMNS is incorrect regarding the views of join using the WITH CHECK OPTION.
For example although the location_id from the TEST_V_2 column appears as non-editable (probably because of the rule that "the columns used in the join expression" cannot be modified in a join view when you use the WITH CHECK OPTION) I can run successfully your insert if statement I choose a location_id less than 2000.
It seems that summed up the difference if you join more than two tables, you'll always get the error "ORA-01733" when you try to insert in the join with the enabled OPTION CHECK view. For example to add a third table TEST_V_2 which does not change the original view, but simply joined meaning for example COUNTRIES to LOCATIONS, will show the same behavior to throw an ORA-01733, however it works fine when the omission of the WITH CHECK OPTION.
So overall, I tend to say it is really a limitation of the implementation and it is not actually an ORA-01402 but looks like Oracle is simply trying to tell you: Amendment No. INSERT in this possible view. Updates however seem to work, at least I can find some examples of work.
There seems to be other restrictions of implementation with the WITH CHECK OPTION in place even when the only membership as two tables, for example when trying to join the COUNTRIES and PLACES but by selecting only in PLACES and by using a filter on the COUNTRY_ID predicate fails with ORA-01733 when this predicate is applied to the COUNTRY. COUNTRY_ID but it works if this predicate is applied to PLACES. COUNTRY_ID.
I could imagine that Oracle has quietly added some of these restrictions with each patch set due to the angle of the case/adverse reactions encountered. I saw this for other features, too.
Kind regards
RandolfOracle related blog stuff:
http://Oracle-Randolf.blogspot.com/SQLTools ++ for Oracle (Open source Oracle GUI for Windows):
http://www.sqltools-plusplus.org:7676 /.
http://sourceforge.NET/projects/SQLT-pp/ -
ORA-01733: virtual column not allowed here
Published by: user8731258 on November 29, 2010 12:45 AMUPDATE ( SELECT callingnumber, calledcallzone, b.callzone callzone, b.ndc FROM (SELECT DISTINCT SUBSTR (connectedcallingnumber, 3, 3) callingnumber, calledcallzone,rownum FROM rating_temp WHERE calltype = 0) a, (SELECT * FROM callzone cc WHERE LENGTH (ndc) = 3) b WHERE callingnumber = ndc ) SET calledcallzone = callzone-----VIRTUAL COLUMN NOT ALLOWED HERE
Its simple you used SEPARATE in your first view inline. And so you cannot use columns for UPDATE.
-
ORA-00984: column not allowed here, when you try to use a default UDF
I am wanting to create a table that has a default value of a user-defined function, and because this default is intended to be used in a few different places so I would use a function rather than in the table definition.
This is my current code that works very well:
but I would get something similar to this work:CREATE TABLE DEPT_HIST ( DEPTNO NUMBER(2) not null, DNAME VARCHAR2(14), LOC VARCHAR2(13), SQL_ACTV_C CHAR(1) not null, EFFT_STRT_S TIMESTAMP(6) default SYSTIMESTAMP not null, EFFT_END_S TIMESTAMP(6) default TO_TIMESTAMP('9999/12/30 00:00:00.000000', 'YYYY/MM/DD:HH24:MI:SS.FF6') not null, DELT_F CHAR(1) default 'N' not null );
but I get an error of:CREATE OR REPLACE FUNCTION EOT RETURN timestamp IS Result timestamp; BEGIN RETURN (TO_TIMESTAMP ('9999/12/30 00:00:00.000000', 'YYYY/MM/DD:HH24:MI:SS.FF6')); END EOT; / select eot from dual; EOT --------------------------------------------------------------------------- 30/DEC/99 12:00:00.000000000 AM CREATE TABLE DEPT_HIST ( DEPTNO NUMBER(2) not null, DNAME VARCHAR2(14), LOC VARCHAR2(13), SQL_ACTV_C CHAR(1) not null, EFFT_STRT_S TIMESTAMP(6) default SYSTIMESTAMP not null, EFFT_END_S TIMESTAMP(6) default EOT not null, DELT_F CHAR(1) default 'N' not null );
Any ideas? I guess I could use a trigger but not exactly what I'm after.EFFT_END_S TIMESTAMP(6) default EOT not null, * ERROR at line 8: ORA-00984: column not allowed here
Hello
Sorry; No function defined by the user in the DEFAULT clause.
From SQL, under "CREATE TABLE Statement" language manual
http://download.Oracle.com/docs/CD/B28359_01/server.111/b28286/statements_7002.htm#sthref7119Restriction on default column values
A DEFAULT expression cannot contain references to the functions PL/SQL or other columns, the nickname CURRVAL, NEXTVAL, LEVEL, PRIOR and ROWNUM, or date constants that are not completely specified.I wouldn't use a trip just for that. If you need a trigger for other reasons, then maybe you can include the definition of this column in the trigger, too, but, in general, avoid triggers when there is an alternative.
-
ORA-00984 column not allowed here. Help, please.
Hey, I made a table;
CREATE TABLE borrower)
BorId VARCHAR2 (5) NOT NULL,
BorName VARCHAR2 (20).
BorMaxBooks NUMBER (10),
KEY elementary SCHOOL (BorId));
I'm trying to enter values in this table;
INSERT the borrower VALUES)
001, 'Jack Jones', 5);
And I get an error; ORA-00984 column not allowed here. Please can someone help? I tried to change the BorName VARCHAR2 (20) BorName char (20), and all I can think about.It should work by specifying your columns like this.
INSERT INTO Borrower (BorId, BorName, BorMaxBooks) VALUES (001, 'Jack Jones', 5);
Sitjà.
-
Operation not allowed on the shipment blocking event thread
Dear friends,
I'm sorry to put this problem, but I'm posting it after much searching this forum. Although the number of threads, the solution is available, but it does not work on me. On a thread, that the person wrote that he solved the problem, but haven't posted the solution how he had done this. The problem is:
SerializableAttribute public class SmsDemo extends net.rim.device.api.ui.UiApplication {}
Private SmsDemoMainScreen SmsDemoMScreen;
Public Shared Sub main (String [] args)
{SmsDemo SmsDemoApp = new SmsDemo();
SmsDemoApp.enterEventDispatcher ();
}
public SmsDemo()
{
_Thread BackGroundThread = new BackGroundThread();
_Thread.start ();SmsDemoMScreen = new SmsDemoMainScreen();
pushScreen (SmsDemoMScreen);
}class BackGroundThread extends Thread {}
public BackGroundThread() {}
/ * initialize the constructor parameters * /.
}public void run() {}
net.rim.device.api.ui.UiApplication.getUiApplication () .invokeLater (new Runnable()
{
public void run() {}
try {}
javax.wireless.messaging.MessageConnection msgConn = (javax.wireless.messaging.MessageConnection)javax.microedition.io.Connector.open("sms://:0");
javax.wireless.messaging.Message msg = msgConn.newMessage (javax.wireless.messaging.MessageConnection.TEXT_MESSAGE);
javax.wireless.messaging.TextMessage = (javax.wireless.messaging.TextMessage) msg txtMsg.
txtMsg.setAddress("sms://+91123456789");
txtMsg.setPayloadText ("Test Message");
msgConn.send (txtMsg);
System.out.println ("sending SMS success!");
} catch (Exception e) {}
System.out.println (e.getMessage ());
e.printStackTrace ();
}
}
});
}
}The code above gives error "Blocking Operation not allowed on the event dispatch thread" to msgConn.send (txtMsg); line.
Please guide me how to solve the problem for example. If possible, please guide me how to continuously listen to the incoming message also. The SmsDemo example with JDE is autonomous work fine but in error when incorporated in my solution.
Thanking you in anticipation.
I don't think you need to do invokeLater (new Runnable()... the inner thread.) Try to remove it, I think that this can cause this problem.
-
Database trigger - PL/SQL: ORA-00984: column not allowed here
I am trying to create a trigger that will update a table of audit used when a row is changed. Using a sequence number to assign an identifier unique to each line as it is created. Need to capture the user ID, date modified and action (update), the image of the front line.
CREATE SEQUENCE emp_audit_seq START WITH 10;
Create table emp ( empno NUMBER(4) Primary Key, ename VARCHAR2(10), job VARCHAR2(9), mgr NUMBER(4), hiredate DATE, sal NUMBER(7,2), comm NUMBER(7,2), deptno NUMBER(2));
CREATE TABLE emp_audit ( audit_uid NUMBER(15) Primary Key, change_date DATE, change_user VARCHAR2(30), action CHAR(1), empno NUMBER(4), ename VARCHAR2(10), job VARCHAR2(9), mgr NUMBER(4), hiredate DATE, sal NUMBER(7,2), comm NUMBER(7,2), deptno NUMBER(2));
Can someone help to help me find what I'm doing wrong with the trigger?CREATE OR REPLACE TRIGGER trig_emp_audit BEFORE UPDATE ON emp FOR EACH ROW BEGIN INSERT INTO emp_audit VALUES(emp_audit_seq.nextval, change_date, change_user, action, :old.empno, :old.ename, :old.job, :old.mgr, :old.hiredate, :old.sal, :old.comm, deptno); END; / Warning: Trigger created with compilation errors. SQL> show errors Errors for TRIGGER TRIG_EMP_AUDIT: LINE/COL ERROR -------- ----------------------------------------------- 2/3 PL/SQL: SQL Statement ignored 3/149 PL/SQL: ORA-00984: column not allowed here
Published by: LostNoob on August 25, 2012 14:24First of all, when you write an INSERT statement, it is always good for the columns that you insert in the list. Which makes the code easier to follow - you do not have separately pull toward the top of the table definition to know what order of columns is inserted. And it makes the code easier to manage because the declaration become invalid if you add a new column to the table in the future.
Second, CHANGE_DATE, CHANGE_USER and ACTION are not (probably) functions and are not local variables so it is not supposed to use them in an INSERT statement. You need to write code or to take advantage of the existing functions to fill in these columns. I suppose, for example, that you want to use SYSDATE to fill the CHANGE_DATE and the USER to fill the column CHANGE_USER. My guess is that ACTION must always be a 'U' for UPDATE.
Thirdly, it seems that you left the: old man on the DEPTNO column.
Put them all together, you would have something like
CREATE OR REPLACE TRIGGER trig_emp_audit BEFORE UPDATE ON emp FOR EACH ROW BEGIN INSERT INTO emp_audit( audit_uid, change_date, change_user, action, enpno, ename, job, mgr, hiredate, sal, comm, deptno ) VALUES( emp_audit_seq.nextval, sysdate, user, 'U', :old.empno, :old.ename, :old.job, :old.mgr, :old.hiredate, :old.sal, :old.comm, :old.deptno); END; /
Justin
-
PL/SQL: ORA-00984: column not allowed here
Sorry, it's probably easy and I forgot something simple, but it's driving me crazy :-)
Error: PL/SQL: ORA-00984: column not allowed here on g_deduction_amountVARIABLE g_fk_deduction VARCHAR2(30) VARIABLE g_fk_empno NUMBER VARIABLE g_before_or_after_flag CHAR(1) VARIABLE g_deduction_amount NUMBER BEGIN :g_fk_deduction := '401K'; :g_fk_empno := 7369; :g_before_or_after_flag := 'B'; :g_deduction_amount := 150.00; END; / BEGIN INSERT INTO emp_deductions (fk_deduction, fk_empno, before_or_after_flag, deduction_amount) VALUES (g_fk_deduction, g_fk_empno, g_before_or_after_flag, g_deduction_amount); COMMIT; END; /
in the value clause.
Any help would be appreciated.
Table is below:
Published by: LostNoob on August 23, 2012 19:06CREATE TABLE emp_deductions ( fk_deduction VARCHAR2(30), fk_empno NUMBER(4), before_or_after_flag CHAR(1), deduction_amount NUMBER(6,2));
rp0428 wrote:
>
: g_fk_deduction: = "401k".
: g_fk_empno: = 7369;
: g_before_or_after_flag: = 'B ';.
: g_deduction_amount: = 150.00;
>
Why did you put a colon here? Get rid of them.They are necessary, since they are declared SQL * more variable.
The problem for the OP, is that in the clause values in the insert the colon are missing.
Published by: Mark Williams on August 23, 2012 22:31
Here is your example requested:
SQL> create table test (c number); Table created. SQL> variable v_c number SQL> begin 2 :v_c := 46; 3 end; 4 / PL/SQL procedure successfully completed. SQL> begin 2 insert into test values (:v_c); 3 end; 4 / PL/SQL procedure successfully completed. SQL> commit; Commit complete. SQL> select * from test; C ---------- 46 1 row selected. SQL>
-
ORA-00984: column not allowed here
Hi all
Kindly someone please shed some light on this called error "ORA-00984: column not allowed here?
I created a table:
CREATE TABLE JB (ENAME VARCHAR (20));
Table created.
Now, if I INSERT:
INSERT INTO VALUES JB (sintes);
ORA-00984: column not allowed here
Why this error, if I insert a number instead of "Sinti", implementation is also possible. No character is not allowed.
What is the column name in this area, its totally strange to me.
Please someone help me.
Thank you and best regards,
SINTESHello
Use quotes around Zack:INSERT INTO JB VALUES ('Sathik');
-
ORA-02287: sequence number not allowed here
< police = "Courier New" >
Hello
Why do I have this problem?
Insert an order tab2 select tab2_seq.nextval, eng_cat from (select distinct job_det eng_cat) by 2.
SQL > r
1 * insert into tab2_seq.nextval select eng_cat select (separate eng_cat tab2
Insert in tab2 select tab2_seq.nextval, eng_cat from (select distinct eng_cat from)
*
ERROR on line 1:
ORA-02287: sequence number not allowed here
Thank you and best regards,
Human
< / make >It's 'order of 2' which makes it fail. That makes no sense at all?
Just remove the order by clause, then it works ;-) -
operation not allowed on java.lang.object
Hello.
I use jdeveloper 11.1.1.5
I had used this code in my AMImpl method
My scenario is to perform this operationViewObjectImpl vo = this.getFinPeriodsView1(); Row vor= vo.getCurrentRow(); System.out.println("Current date : " + (vor.getAttribute("FpFromDate") + 1) //getting error as operation not allowed on java.lang.object + "-" + now.get(Calendar.DATE) + "-" + now.get(Calendar.YEAR));
select max(add_months(fp_from_date,1)) from fin_periods //This value is to be set to FPFromDate Attribute for FinPeriods
I need to do this for 12 periods that example sample isselect max(add_months(fp_end_date,1)) from fin_periods //This value is set to be set to FpEndDate Attribute for FinPeriods
How can I do this in my method of AMIMpl.for (int i=0;i<=12;i++) { select max(add_months(fp_from_date,1)) from fin_periods; select max(add_months(fp_end_date,1)) from fin_periods; }
Hello
First add after the stuff inside your implementation code//Code Stuff in your mathod as follows Calendar cl = Calendar.getInstance(); java.util.Date dateFromTable = convertDomainDateToUtilDate((oracle.jbo.domain.Date)vor.getAttribute("FyStartDate"));//check now cl.setTime(dateFromTable); System.out.println (cl.getTime()); cl.add(Calendar.DATE, 30);//add 30 days Date toDate = cl.getTime(); System.out.println (toDate); //
and also add convertDomainDateToUtilDate new method to your class. Method will return java.util.Date to your oracle.jbo.domain.Date
public java.util.Date convertDomainDateToUtilDate(oracle.jbo.domain.Date domainDate) { java.util.Date date = null; if (domainDate != null) { java.sql.Date sqldate = domainDate.dateValue(); date = new Date(sqldate.getTime()); } return date; }
Maybe you are looking for
-
What are the compatible motherboards for Satellite A30 213
Hello This is my first post, I hope someone can help me! I have a laptop A30-213, which requires a new main Board.Can someone tell me that other models in this series have compatible motherboards?I note there are a few on Ebay but no saying specifica
-
Saludos. I have a project in el cual por medio a cluster obtengo varios numericos, characters padlock, boleanos etc. data types, (para poder guardarlos en un .txt using el al final todos los convierto string, write in a text file) is tengo el vi solo
-
How can I uninstall windows 7 and return to windows vista?
Uninstall windows 7 Home premium How to uninstall windows 7 Home premium package and re install windows vista Home premium SP1
-
OGG, dll not ther
-
X 200 Bluetooth problem - appliance power on/off do not
I recently bought a 2nd hand X 200. I tried everything to activate and get the job of bluetooth. It only comes up in Device Manager. I checked behind the bezal screen to see if the ITO is here! I installed all the relevant software Vantage think that