I'm trying to use Elmah on one of my recent project.
I'm using an oracle database so I got the oracle script for Elmah, but I'm sure I'm doing something wrong because when I run the scrip I get this error:
Any ideas?
Thank for your time!
Related
Forbidden
The requested operation is not allowed
I have created new application and getting above error while running app on local server
Old Question, but this might help others:
Seems like the friendly URL feature introduced in APEX 20.1 is causing this issue. A workaround for me is just disabling that in the Application Definition Atrributes.
I had the same problem after upgrading from Oracle Apex 19.2 to Oracle Apex 20.2. I tried everything and nothing happened. I found this:
https://docs.oracle.com/en/database/oracle/application-express/20.1/htmrn/index.html#HTMRN-GUID-175AC460-3BCB-4871-A14C-5A232EDF8CAD
I'm not sure if this is the case, but I can't find any other explanation - in section 2.1.1 Oracle Database Requirement it is said that version 20.2 is compatible with database version 11.2.0.4 and above. Mine is 11.2.0.3. Probably doesn't work for that. Check your version of the database and share if you are below the required one to know if I guess correctly. If so, and you want APEX 20.2, you may need to update your database version first, if a possible.
I hope I helped.
I've downloaded oracle database and when I click on get started I get this message , how can I fix it ?
This usually means you haven't started a database.
I am using Oracle SQL Developer version 4.1.0.19.
So this can be a very simple issue but I cannot seem to find the solution anywhere as I have just started using SQL Developer.
I type in this query
create table Student(Stu_id INTEGER,Stu_name VARCHAR(60),Stu_email VARCHAR(60))
select * from Student
And when I Run the SELECT query, I get an error something like this:
Method oracle/jdbc/driver/T4CCallableStatement.isClosed()Z is abstract
I have no idea as to why this is happening , this may be very stupid but I cannot seem to find a solution.
BTW I am using Oracle 11g version.
How did you install SQL Developer? Can you download the zip off of OTN and extract it to a fresh directory and try running it from there?
Your error message indicates something VERY bad is wrong with one of the drivers. Which makes me wonder if you messed with one of the JARs or are attempting to use an old Oracle Client with a THICK connection.
I have successfully installed Oracle REST Database Services version 3.0.4.60.12.48. I am able to access Oracle Apex but when I create a web-service and click on test button I get this error.
Error during evaluation of resource template: GET hr/employees/,
SQL Error Code: 28000,
SQL Error Message: ORA-28000: the account is locked
I have tried connecting to Oracle_apex_public user and every other user to check if any account is locked but I am able to connect to these account with SQLDeveloper.
I have also tried reinstalling and changing default tablespace inside ORDS configuration files, but still it's not working.
If anyone has an idea what is going wrong, please help.
Thank you for the response.
I manage to solve the issue, the cause was i was using same Passwords for all apex public and sys changing th
I have a web app hosted on BEA Weblogic 10.x with an Oracle 10g database backend.
It works perfectly with one database, but when we make a clone of it and try to use a different WebLogic and Oracle instance we are getting this error:
ERROR - Problem initializing invocation tracking - disabling
tracking xxxxclass.BadTableMappingException: Database column
xxxxPeriodEnding in database yyyyyyy, table zzzzzzz has an
unknown type: JDBC Type 91.
We get it every time we do a query that involves a column of type DATE. There was no ORA-XXXX code in the message.
I can access the database using SQL*Plus using the same access and do selects and updates on the same tables with no errors.
The answer to this question is not just a simple description of what a type 91 error is (although that will help) but what could be causing this given the circumstances described above.
I am using ojdbc14.jar for JDBC on both instances of weblogic.
I have no idea about the error, but have you considered the jdbc jar version and more importantly if the oracle DB needs to be updated.
I faced very weird problems with oracle, and struggled for a while to find at the end that installing some patches for oracle would solve the problem.
Set oracle.jdbc.V8Compatible=true.
This remaps the oracle DATE type to a DATETIME time in JDBC. This parameter was missing on the new Weblogic server.