SQL Error

[Sno]

Seems basic, but I keep getting Invalid Character

Connection con = Utility.getOracleConnection();
String SQL = "SELECT ORDERED FROM AGG_SLR_SUMMARY;";
Statement stmt = con.createStatement(ResultSet.TYPE_SCROLL_SENSITIVE, ResultSet.CONCUR_READ_ONLY);
ResultSet rs = stmt.executeQuery(SQL);

Error:

16:38:28,010 INFO  [STDOUT] SQLException() - ORA-00911: invalid character
16:38:28,010 INFO  [STDOUT] java.sql.SQLSyntaxErrorException: ORA-00911: invalid character

If I change this statement without the ;

String SQL = "SELECT ORDERED FROM AGG_SLR_SUMMARY";

I get the error

16:28:51,807 INFO  [STDOUT] SQLException() - ORA-00942: table or view does not exist
16:28:51,807 INFO  [STDOUT] java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

I've connected to this database before with a CallableStatement for a package.procedure...

Am I missing something here?

[PhHein]

String SQL = "SELECT ORDERED FROM AGG_SLR_SUMMARY;";

That semicolon inside the sql String seems very suspicious.

Did you forget an owner/ schema name?

[Sno]

owner/ schema name which you reference is in the Utility.getOracleConnection(); method that I call.

I am not at work anyone, which I was doing this, looking back at my personal project code. This worked for me in the past

//PHPmyAdmin Database
Statement st = conn.createStatement();
ResultSet res = st.executeQuery("SELECT * FROM  `eossysdef`;"); // SQL Grab Table

i'll try that tomorrow, and I have played with that semi-colon, it was suspicious to me as well.

[Tolls]

The PHPMyAdmin driver is probably quite lenient.
The semi-colon isn't needed.

Anyway, "table or view doesn't exist" is pretty clear.
Ensure you are looking at the correct db.
Ensure that db has that table.
Is that table part of the user schema you are logged in as?
If not then I'd recommend, as already suggested, adding the schema name in the query.

[Sno]

... I think I found my problem. Yesterday morning before I dropped an xml file named oracle-ds.xml that held my QA database info. I ended up overwriting my development database info.

So I'm about to determine if that was the actual issue.

[Sno]

Yup. It was exactly the overwrite I perform yesterday.

[PhHein]

Solved?:rolleyes:

[Sno]

Totally!!1!