How are you running the import? From the gui? the blcli? from a workstation to the appserver or direct from the appserver? what is the network between the appserver and system running the import?
imports from blcli or from the gui last the same.
It is slow since last week. Imports of nsh scripts are fast.
I will check the network between the 2 servers.
Can a restart of the application server resolve this issue ?
It would make sense to try and determine why it’s happening, in the even that it happens again – if you are able to spend the time diagnosing it. a restart could fix it, but I would guess that might only be temporary.
my 2 application servers have been rebooted. I have the same problem. The network between the 2 servers is good (good transfer tests: 15MB/s => ~150Mb/s). The DBAs don't see anything abnormal on the database. I will ask for an AWR report.
What about between the appserver and file server?
When you upload the file it should go from the system w/ the file to the appserver then to the file server. the only writes to the db should be to create the package operation and that should be pretty fast. So this seems like either a network or disk problem.
Bad news from the support : the problem is due to a too big table in the database, and the cleanups in 8.0 don't work. The support don't find any solution for the moment.
What is wrong w/ the cleanup? what cleanup are you running? what support issue is this ?
the support explained that :
SQL> select count(*) from bl_value where data_type_id = 1048 and
Which means the index on BL_VALUE in the query has to initially handle unwanted 41k rows, although those are later on filtered by is_deleted=0 condition.
Cleaning up the Database would remove these 41k records which shall improve the query performance considerably. But the DB_CLEANUP in 8.0 does not work
What issue # is this ?
What version of 8.0 is this? what specifically is not working wrt cleanup here ?
Bill, the ticket is #ISS03921365
We are in 8.0SP9 , the db cleanup job executes during 3 days without deleting data. The support developped a patch for this problem but it does not resolv our problem.
The problem seems to be resolved in 8.2.