There are three ways we can use on WHERE clause on SQL:
orwhere column_name = nvl(:parameter, column_name)
orwhere column_name like nvl(:parameter, '%')
where (column_name = :parameter or :parameter is null)
orwhere column_name = nvl(:parameter, column_name)
orwhere column_name like nvl(:parameter, '%')
where (column_name = :parameter or :parameter is null)
Then you can kill it with (change sid and serial# using result from query above):select s.username,s.sid,s.serial#,s.last_call_et/60 mins_running,q.sql_text from v$session s
join v$sqltext_with_newlines q
on s.sql_address = q.address
where status='ACTIVE'
and type <>'BACKGROUND'
and last_call_et> 60
order by sid,serial#,q.piece
ALTER SYSTEM KILL SESSION 'sid,serial#';
change archivelog until time 'sysdate-x' delete;
Unable to start oafm using adstrtal.sh. Running adoafmctl.sh ends with timeout.
You are running adoafmctl.sh version 120.6.12000000.3
Starting OPMN managed OAFM OC4J instance ...
adoafmctl.sh: exiting with status 152
Solution:
Clear the TLD cache:
- stop all middle tier services
- Delete/backup files this file:
$COMMON_TOP/_TldCache
- start all middle tier services
ORA-01017: invalid username/password; logon denied ORA-02063: preceding line from %sI checked the connection using sqlplus, worked. Using connection description on sqlplus, also worked fine. I even recreated the database link, but still failed.
ADMN-705021Just run %ORACLE_HOME%\dcm\bin\dcmctl shutdown and retry the patch.
The configuration files for this Oracle Application Server instance are inconsistent with the
configuration stored in the repository. In order to protect the repository,
no further configuration or deployment operations are allowed until the problem with the configuration on the filesystem is resolved. This condition arises when a prior operation was unsuccessful. The exception associated with this failed operation is:
{0}
. Please also check the logs located at
ORACLE_HOME/dcm/logs to determine why DCM was unsuccessful in updating
the configuration files on disk. Some possible causes are:
* permissions on files
* file contention issues on Windows NT
* internal Oracle error
After resolving the problem that prevented DCM from updating the configuration
files, you may use the dcmctl resyncInstance command to resolve the problem.
Alternatively, you can stop and then restart the active dcmctl or EMD
process and resyncInstance will automatically be performed.
Resolution:
Base Exception:
Transaction failed in Plugin cannot rename old configuration file:e:\OMS\oms10g\diagnostics\config\logloader.xml.
Resolution:
Transaction failed in Plugin.
select invoice_id from ap_invoices_all where invoice_num='your invoice number'3. Verify that your invoice is a corrected invoice using
select invoice_id, line_number from ap_invoice_lines_all where invoice_id = corrected_inv_id4. You should see your invoice_id on the result, if not then you are facing another problem.
update ap_invoice_lines_all set corrected_inv_id=null where invoice_id='your invoice id from step 2' and line_number='line number from step 3'6. Don't forget to commit.