DAC has 19 inactive sessions in Repository Database

Is this normal for the DAC to leave open 19 inactive sessions in the Repository Database when it is not running? Some of the last statements it ran were: SELECT SYSDATE FROM DUAL, etc
Shouldn't it close some of these sessions when not running? I understand that it should leave open at least 1 so that it can fulfill it's 'Heartbeat Interval' requirements.
Any insight into this issue would help greatly.
Thanks,
Andy

can you upload a screenshot of DAC to explain your question?

Similar Messages

Inactive sessions increasing in database

Hi
Recently i migrated Oracle9i database to oracle10g database 64 bit on windows 2008 server.
After Migration.Inactive sessions are not automatically flushing from database,and these inactive sessions are reaching maximum sessions limits that leads to Database Hang.
How can i solve this inactive sessions problem?
Thanks
With Regards
OH

damorgan wrote:
desc sys.kottd$Interesting table and custom data type.
SQL> set long 9999
SQL> col SQL format a50
SQL>
SQL> select
2          DBMS_METADATA.get_ddl( 'TABLE', 'KOTTD$', 'SYS')        as SQL
3 from       dual;
SQL
CREATE TABLE "SYS"."KOTTD$" OF "SYS"."KOTTD"
OIDINDEX ( PCTFREE 10 INITRANS 2 MAXTRANS 255
STORAGE(INITIAL 65536 NEXT 1048576 MINEX
TENTS 1 MAXEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFF
ER_POOL DEFAULT)
TABLESPACE "SYSTEM" )
PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS
LOGGING
STORAGE(INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MA
XEXTENTS 2147483645
PCTINCREASE 0 FREELISTS 1 FREELIST GRO
UPS 1 BUFFER_POOL DEFAULT)
TABLESPACE "SYSTEM"
SQL>
SQL>
SQL> select
2          DBMS_METADATA.get_ddl( 'TYPE', 'KOTTD', 'SYS')        as SQL
3 from       dual;
ERROR:
ORA-31603: object "KOTTD" of type TYPE not found in schema "SYS"
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.DBMS_METADATA", line 2805
ORA-06512: at "SYS.DBMS_METADATA", line 4333
ORA-06512: at line 1
no rows selected
SQL>
SQL> col attr_name format a30
SQL> col attr_type_name format a30
SQL> select
2          attr_no,
3          attr_name,
4          attr_type_name
5 from       dba_type_attrs
6 where      type_name = 'KOTTD'
7 and        owner = 'SYS'
8 order by attr_no;
   ATTR_NO ATTR_NAME                      ATTR_TYPE_NAME
         1 KOTTDKVN                       UNSIGNED BINARY INTEGER(32)
         2 KOTTDSCH                       VARCHAR2
         3 KOTTDNAM                       VARCHAR2
         4 KOTTDUVN                       VARCHAR2
         5 KOTTDTC                        UNSIGNED BINARY INTEGER(16)
         6 KOTTDTDS                       CANONICAL
         7 KOTTDNDS                       CANONICAL
         8 KOTTDFLG                       UNSIGNED BINARY INTEGER(16)
         9 KOTDVSN                        UNSIGNED BINARY INTEGER(16)
        10 KOTTDBDY                       KOTTB
10 rows selected.
SQL> -- not even a varchar2 attr of the data type "accessible"
SQL> select KOTTDNAM from sys.kottd$ where rownum < 11;
select KOTTDNAM from sys.kottd$ where rownum < 11
ERROR at line 1:
ORA-00904: "KOTTDNAM": invalid identifier
SQL> -- Calling the constructor? Oracle no likes..
SQL> select KOTTD( null, 'test','test','test',null,null,null,null,null,null) from dual;
select KOTTD( null, 'test','test','test',null,null,null,null,null,null) from dual
ERROR at line 1:
ORA-00600: internal error code, arguments: [qctcte1], [0], [], [], [], [], [], []
SQL>

Inactive sessions in Database

Hi,
Lot inactive sessions are in database, Before we bounce database ----> max process got reached, For that we have changed max process and bounced the database but i can see still 75 inactive sessions in database,
SQL> show parameter process
NAME TYPE VALUE
aq_tm_processes integer 1
db_writer_processes integer 1
gcs_server_processes integer 0
job_queue_processes integer 2
log_archive_max_processes integer 2
processes integer 200
SQL> show parameter spfile
NAME TYPE VALUE
spfile string
Then i changed processes to 300
SQL> show parameter process
NAME TYPE VALUE
aq_tm_processes integer 1
db_writer_processes integer 1
gcs_server_processes integer 0
job_queue_processes integer 2
log_archive_max_processes integer 2
processes integer 300
even after bouncing still 75 inactive sessions in database

Hi,
What are the events/programs of those sessions?
Have you started the application or not yet?
Go through the following documents and see if it helps.
Note: 427759.1 - How To Prevent Inactive JDBC Connections In Oracle Applications
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=427759.1
Note: 261791.1 - 11i JDBC Thin client connections remain active, MAX PROCESSES REACHED
https://metalink2.oracle.com/metalink/plsql/ml2_documents.showDocument?p_database_id=NOT&p_id=261791.1
Regards,
Hussein

Inactive sessions

Iam in need of a script to kill all the inactive sessions in the database and the same script should kill all the pid related in the OS also.
can anyone send me a scripts or any input on this will be of great help ?
Kai

KaiS,
See both functions and wrap around in your unix script, this should magic for you I suppose :) and you should replace sqlplus "/as sysdba" by sqlplus '/as sysdba'
*function readSqlstmt {*
typeset stmt=$1
echo "
set feedback off
set verify off
set heading off
set pagesize 0
whenever sqlerror exit 1
whenever oserror exit 2
*$stmt;*
exit
*" | sqlplus -S "/as sysdba" >> test.log*
function killpid {
killpidsql=killpid.sql
sqlplus -s "/as sysdba" << ENDOFSQL >> test.log
whenever sqlerror exit 1
whenever oserror exit 2
SET pagesize 0
SET verify off
SET feedback off
SPOOL ${killpidsql}
SELECT 'ALTER system kill session ''' || s.sid || ',' || s.serial# || ''';'
FROM v\$session s, v\$process p
WHERE s.paddr = p.addr AND s.status = 'INACTIVE';
SPOOL OFF
@${killpidsql}
ENDOFSQL
Example: How to use above readSqlstmt function, to kill unix process id and call "killpid" to kill sessions from oracle.
*readSqlstmt "SELECT p.spid FROM v\$session s, v\$process p WHERE s.paddr = p.addr AND s.status = 'INACTIVE'" | while read u*
*do*
* #echo "kill -9" $u >> test.log*
* echo $u*
*done*
*Regards*
Edited by: OrionNet on Dec 10, 2008 10:52 PM
Edited by: OrionNet on Dec 10, 2008 10:54 PM

OracleConnectionPoolDataSource creates inactive sessions

Hi,
My customer uses OracleConnectionPoolDataSource and finds that the pooled connection had created a huge number of inactive sessions on the database side.
Any idea why this happens?
Thanks in advance.
Regards,
Sindhiya V.

Hi Hamdy,
The inactivity timeout was configured through the Oracle Enterprise Manager.
We created a Data Source and specified the following attributes on the page.
JNDI Locations
Location: jdbc/USPSTFPDADefaultDS
XA Location: jdbc/xa/USPSTFPDAXADS
EJB Location: jdbc/USPSTFPDADS
Connection Attributes
Connection Retry Interval: 5
Max Connection Attempts: 3
Cached Connection Inactivity Timeout: 300
Maximum Open Connections: 10
Minimum Open Connections: 1
Wait For Free Connection Timeout: 5
Hope you could help me in resolving this issue.
Thanks & Regards,
Sindhiya V.

DI 11.5.3 created inactive repository sessions on the database server

The cusotmer complaint that many inactive sessions have been created on their DI repository database. As a result, the database has to be bounced every 3 or 4 days to clean those sessions. They use DI 11.5.3 on HP-UX. The database is Oracle 10g. What would cause this issue? The improper close of the Desinger window? Or something wrong with the job design?
Thanks,
Larry

what is the process or application to which these sessions belong, Designer is not the only application which will open repo connection. WebAdmin also open connection to repository, it actually opens multiple connection
I think you can get the application and process which have opened session to the database from v$sessions table

Inactive sessions increasing database

Hi
We are using oracle11.5.10.2 on windows 2000 server and database version 10.2.0.3
we are facing problem with inactive sessions,grdually inactive sessions increasing and thats leads database crash.
Temporary i increased processes parameter value tp 400 prviously it was 200
Most of inactive session from apps user only
How can i fix this problem?
Thanks
With Regards
OH

Hi,
Please see these threads.
how to kill inactive sessions????????
how to kill inactive sessions????????
Inactive sessions in Database
Re: Inactive sessions in Database
Regards,
Hussein

Database Status Inactive Sessions

On OAM Applications Dashboard > Navigate to "DATABASE STATUS" > Sessions "#"
I see alot of inactive sessions. Is it okay to terminate all of the inactive sessions? does it affect system performance? THanks!
Message was edited by:
chaseeem

Oracle will clean them up for you. In addition, you could terminate a session that's simply idle.

Inactive Sessions Getting Automatically Generated in Database

I am facing a strange problem of getting huge number of inactive sessions getting generated th the database server which leads to it's connection closure.
The Error reads as "Failed to check out an Application due to connection failure of Application Module."
This happens each time I execute the following code:
String amDefName = "amendprgo.model.CSDInvFRCAmendPrgoServices";
String configName = "CSDInvFRCAmendPrgoServicesLocal";
ApplicationModule app1 = Configuration.createRootApplicationModule(amDefName,configName) ;
String voInstanceName="prgoHdrRO";
ViewObject prgoHdrROVO =app1.createViewObjectFromQueryStmt(voInstanceName,"select * from INV_PRGO_HDR");
prgoHdrROVO.setWhereClause("PRGO_ID="+tempRow.getAttribute("PrgoId")+" and DEPOT_CD = '0' and ITEM_CAT = 'I3' ");
prgoHdrROVO.executeQuery();
if(prgoHdrROVO.getEstimatedRowCount()>0){
return true;
I know there is a process of creating connection and View Object in Model part in JDeveloper, but I want to know why this problem happens.

ApplicationModule app1 = Configuration.createRootApplicationModule(amDefName,configName) ;is your problem as it causes at least one (sometimes more) connections to open. As you don't free the resource after using it the connection remains open even if you can't access it anymore.
You should call Configuration.releaseApplicationModule(...), with the application module you created before returning.
On the other side you shoulnd not even call createRootApplicationModule in the first place (as it causes trouble if you don't deeply know what the framework do with a root application module).
Can you tell us the use case which make you call createRootApplicationModule()? We might find a better solution.
Timo
Edited by: Timo Hahn on 19.05.2011 13:45
PS: something to read http://blogs.oracle.com/jdevotnharvest/entry/when_to_use_createrootapplicationmodule_in_oracle_adf and http://radio-weblogs.com/0118231/2009/08/20.html#a959

So many INACTIVE sessions in Database

Hi,
Actually PMON will clears all inactive sessions from database.
But i can see there are sessions like more then 3,4 days old.
Why PMON is not clearing them. ?
On which intervals will PMON do inactive sessions cleaning.
thanks in Advance.

>
But i can see there are sessions like more then 3,4 days old.
>
Heed the advice of the other responders.
But for idle sessions that you want cleared immediately you can use
ALTER SYSTEM DISCONNECT SESSION . . . IMMEDIATENOTE - this acts differently than the 'KILL SESSION' syntax typically used.
See 'DISCONNECT SESSION' clause in the SQL Language reference section for ALTER SYSTEM
http://docs.oracle.com/cd/B28359_01/server.111/b28286/statements_2013.htm
>
Use the DISCONNECT SESSION clause to disconnect the current session by destroying the dedicated server process (or virtual circuit if the connection was made by way of a Shared Sever).
The IMMEDIATE setting disconnects the session and recovers the entire session state immediately, without waiting for ongoing transactions to complete.
>
Then contrast that with the text for KILL SESSION

Inactive sessions in v$session. True problem

Hi,
I am working in an Oracle 9i/Weblogic/J2EE platform. And when i look for session info in v$session view, i see that there are many sessions that have a status "Inactive". I already figured out what it means- the session is ACTIVE when it is doing an SQL query at the time and the session is INACTIVE when it is not doing an SQL query at that particular moment.
But i have questions:
1) If a client logs in to my webapplication and does a SQL query- then the sessions status is ACTIVE. After that, when the client just leaves (logs out just closes the browser) then Oracle marks that connection as 'INACTIVE'- Oracle does not KILL that session.
Ok let that be, but can another client then log in to my webapplication (from different computer) and get that same INACTIVE connection and start to use it?? If not, then these "abandoned" connection are truly useless, because they still use ORACLE resources (memory).
2)Another thing is that there are many INACTIVE sessions in v$session that have a name "plsqldev.exe" in PROGRAM column. That is a database client that i use to connect directly to my DB. But basicly i have only one PL/SQL program with one SQL query window open (this session is marked ACTIVE in v$session). So are these other 10 INACTIVE "plsqldev.exe" sessions meant for new plsql clients that may start to use the database or can only that particular user for whom the session was created at first place use that session?
And finally- sessions that are INACTIVE and have "plsqldev.exe" as a PROGRAM in v$session - is there any chance that a client logs in to webapplication and then gets that INACTIVE session?
If not, then these 10 INACTIVE plsqldev sessions (allthough the user has maybe shut down the program) are wasteless for webapplication users and they just starve the database.
Also a screenshot for illustration.
Waiting for your comments,
Thanks!

If connection pooling is in use then yes a different end-user can reuse the "inactive" session. Remember that ACTIVE and INACTIVE really only refers to if the session is executing SQL at the exact moment you query v$session.
In the case of a dedicated user connection using a product like Oracle Forms where the user spends much of the time reading and filling in screen fields the Oracle background session can show INACTIVE almost constantly because the queries being ran by the user are very fast.
Take a look at the last_call_et column. This is the time in seconds from when the last SQL statement was issued (not completed). If this value is resetting then the queries are being done.
If the time is large and the status is INACTIVE then you could have a 'dead' or 'runaway' background process which is a background process without a front-end process. Those can and should be terminated. For that matter sessions that are idle for long periods of time should probably also be killed. If nothing else runaway and idle sessions may make it appear you are using all your licensed connections even if you really are not.
Most connection pools wil automatically restart a terminated connection so if you clean-up process terminates an idle pooled connection it should not be a problem.
HTH -- Mark D Powell --

Disconnection leaves inactive sessions

Hi I am new to this forum, I have looked but cannot find any reference to my problem, apologies if it has been discussed earlier.
When in SQLDev (EA2 and also earlier versions) on windows2000prof v5 sp4, when I disconnect from a connection inactive sessions are still on the DB (9i r2), this for reasons I won't go into here causes us problems. We have to save all our work and exit sqldev then restart to ensure connections disappear.
I assume this is so connections are reused if you reconnect, and on the face of it seems reasonable, however, it is a problem for us.
Is there some config I can do to stop this behaviour either by connection or for all connections ?
Help appreciated.
btw really like this product, EA2 now has support for AQ's and Materialised views which we use ( we have now decided not to renew TOAD licences because sqldev seems to be mature enough for our purposes now - and is cheaper :-) )
Message was edited by:
CharlieColson

Many thanks for your reply.
I am not doing anything special, it must be designed behaviour because as soon as I exit sqldev the sessions are gone :-
open a connection
run some sql in a worksheet, close worksheet
disconnect from the connection using the connection tree
inactive sessions remain on the database, one for connection and one for insight.
I was hoping that there is some java/config/connection setting I could use, it dosen't happen from TOAD so I can't think it is server behaviour ( and neither does my DBA ).
Cheers

Growing Number of Inactive Sessions

When using WebDB application with 1.)Oracle Application Server 4.8.1 or 2.)Oracle 9i Application Server (Authentication Mode Basic) I noticed many sessions with status inactive in database.
What is the methodology to logout the session from application and avoid growing number of inactive sessions?
null

-- Submits a dbms_job to cleanup sessions
-- Expected Parameters:
-- 1. hours_old - number of hours after session start before
-- it should be deleted
-- 2. start_time - when should the first job be run or 'START'
-- 3. start_time_fmt - date format for start time
-- 4. interval_hours - how many hours between each run
-- If 'START' is provided for 2nd parameter, the 3rd parameter is
-- ignored and it will default the start time to the current time.
set serverout on
set verify off
create or replace package wwctx_patch is
procedure cleanup_sessions
p_hours_old IN number default 168 -- (1 week)
end wwctx_patch;
show errors package wwctx_patch;
create or replace package body wwctx_patch as
* cleanup expired sessions
procedure cleanup_sessions
p_hours_old IN number default 168 -- (1 week)
is
cursor expired_sessions is
select rowid
from wwctx_sso_session$
where active = 0
or (session_start_time < sysdate - (p_hours_old/24));
current_session expired_sessions%rowtype;
record_count number := 0;
begin
if p_hours_old is null then
return;
else
open expired_sessions;
loop
fetch expired_sessions into current_session;
exit when expired_sessions%notfound;
record_count := record_count + 1;
delete from wwctx_sso_session$
where rowid = current_session.rowid;
-- Note: The reason for doing this deletion in
-- a loop with a commit in the loop is so as not
-- to overrun the rollback segment in the case
-- where there are a lot of sessions to cleanup
-- with potentially a large amount of session
-- storage to be deleted.
-- do more than one per commit
if record_count >= 10 then
commit;
record_count := 0;
end if;
end loop;
close expired_sessions;
commit;
end if;
exception
when others then
rollback;
end;
end wwctx_patch;
show errors package body wwctx_patch
declare
INVALID_DATE_EXCEPTION exception;
INVALID_AGE_EXCEPTION exception;
INVALID_INTERVAL_EXCEPTION exception;
v_jobid binary_integer;
v_path varchar2(100) := 'oracle.portal.session';
v_name varchar2(100) := 'cleanup_jobid';
v_starttime date;
v_hours_old number;
v_interval_hours number;
p_hours_old varchar2(30) := '&1';
p_start_time varchar2(60) := '&2';
p_start_time_fmt varchar2(60) := '&3';
p_interval_hours varchar2(60) := '&4';
begin
-- validate hours_old parameter
begin
v_hours_old := to_number (p_hours_old);
exception
when others then
raise INVALID_AGE_EXCEPTION;
end;
-- validate starttime
begin
if upper(p_start_time) = 'START' then
v_starttime := sysdate;
else
v_starttime := to_date (p_start_time, p_start_time_fmt);
end if;
exception
when others then
raise INVALID_DATE_EXCEPTION;
end;
-- validate interval_hours parameter
begin
v_interval_hours := to_number (p_interval_hours);
exception
when others then
raise INVALID_INTERVAL_EXCEPTION;
end;
-- Create a preference store item for the job id that is
-- created for the submitted job.
-- This will allow it to be deleted or modified later.
begin
WWPRE_API_NAME.CREATE_PATH(v_path);
commit;
dbms_output.put_line ('Created path for job id.');
exception
when WWPRE_API_NAME.DUPLICATE_PATH_EXCEPTION then
-- probably this has already been created and a job
-- is already in place.
-- retrieve the job id
null;
when WWPRE_API_NAME.GENERAL_PREFERENCE_EXCEPTION then
dbms_output.put_line
('ERROR: Exception in preference path creation');
raise;
when others then
dbms_output.put_line('ERROR: creating path - ' | | sqlerrm );
raise;
end;
begin
v_jobid := WWPRE_API_VALUE.GET_VALUE_AS_NUMBER
p_path => v_path
,p_name => v_name
,p_level_type => WWPRE_API_VALUE.SYSTEM_LEVEL_TYPE
dbms_output.put_line ('DBMS_JOB id = ' | | v_jobid );
exception
when WWPRE_API_NAME.NAME_NOT_FOUND_EXCEPTION then
-- we'll try to create it below.
null;
end;
if v_jobid is null then
begin
WWPRE_API_NAME.CREATE_NAME
p_path => v_path,
p_name => v_name,
p_description => 'The job id of the DBMS_JOB for cleaning up '| |
'the expired session rows.',
p_type_name => 'NUMBER',
p_language => WWNLS_API.AMERICAN
commit;
exception
when WWPRE_API_NAME.DUPLICATE_NAME_EXCEPTION then
null;
when OTHERS then
dbms_output.put_line('ERROR: creating name - ' | | sqlerrm );
raise;
end;
end if;
declare
l_job varchar2(4000);
begin
l_job :=
'begin ' | |
' execute immediate ' | |
' ''begin wwctx_patch.cleanup_sessions(' | |
' p_hours_old => ' | | v_hours_old | |
' ); end;'' ' | |
' ; ' | |
'exception ' | |
' when others then ' | |
' null; ' | |
'end;';
if v_jobid is null then
DBMS_JOB.SUBMIT
job => v_jobid,
what => l_job,
next_date => v_starttime,
interval => 'SYSDATE + ' | | v_interval_hours | | '/24'
WWPRE_API_VALUE.SET_VALUE_AS_NUMBER
p_path => v_path,
p_name => v_name,
p_level_type => WWPRE_API_VALUE.SYSTEM_LEVEL_TYPE,
p_level_name => null,
p_value => v_jobid
commit;
DBMS_OUTPUT.PUT_LINE ('Cleanup job submitted.' | |
' Job ID = ' | | v_jobid);
else
-- v_jobid is not null
-- modify the job
DBMS_JOB.CHANGE
job => v_jobid,
what => l_job,
next_date => v_starttime,
interval => 'SYSDATE + ' | | v_interval_hours | | '/24'
commit;
DBMS_OUTPUT.PUT_LINE ('Cleanup job updated.' | |
' Job ID = ' | | v_jobid);
end if;
if p_start_time_fmt = 'NOW' then
DBMS_JOB.RUN
job => v_jobid
commit;
DBMS_OUTPUT.PUT_LINE ('Cleanup job run.');
end if;
end;
exception
when INVALID_DATE_EXCEPTION then
rollback;
DBMS_OUTPUT.PUT_LINE ('ERROR: Start Date Specified is Invalid');
when INVALID_AGE_EXCEPTION then
rollback;
DBMS_OUTPUT.PUT_LINE ('ERROR: Age For Cleanup Specified is Invalid');
when INVALID_INTERVAL_EXCEPTION then
rollback;
DBMS_OUTPUT.PUT_LINE ('ERROR: Job Interval Specified is Invalid');
when OTHERS then
rollback;
DBMS_OUTPUT.PUT_LINE ('ERROR: ' | | sqlerrm );
end;
set verify on

SBO Ent XI 3.1 SP3 repository database access error

Dear Experts,
We are installing XI SP3 and using oracle 10g for repository database, we've installed 10.2.0.4 oracle db on windows 2008,
tnsping is working, but we are getting following error ;
Database access error. Reason Loading shared object failed. First tried to load library oci and failed because of error: [%1 is not a valid Win32 application.
]. Second tried to load library oci.dll and failed because of error: [%1 is not a valid Win32 application.
Problems installing Xi 3.1 sp3 with Oracle DB
Same problem solve via using 32bit oracle client, how can i instalee 32 bit oracle client, because oracle path's using ths insttalion directory on same server,
Could you please wirte the steps for how to install oracle client for boe on the same server via 64 bit oracle home
Best Regards

BusinessObjects is not a 64-bit application. It is a 32-bit application that can be run on a 64-bit server. My experience has been that because it is a 32-bit application, it will not work with 64-bit database drivers. For example, we have to set up 32-bit ODBC connections in order to connect to MS SQL Server even though the server where BOE is installed is a 64-bit server.
-Dell

Configuration Manager Error - (-9986)Session to local database...

Hello guys, I'm with a little problem.
When I try to open the Configuration Manager in a Sprowler Server, and appears this error: (-9986)Session to local database could not be opened.
But i try to resolve this problem at ODBC Connection (ODBC Data Source). But all connections is ok.
I saw that some processes of distributor are oscillating(Distributor rclient). So I saw in distributor log this error:
10:24:49 dis-nm ICM\ucce\Distributor node error checking health of process rtc.
Last API Error [109]: The pipe has been ended.
10:24:49 dis-nm Process rtc on ICM\ucce\Distributor is down after running for 0 seconds. It will restart after delaying 1 seconds for related operations to complete.
But in SQL Server, the Named Pipes is enable, in second position. I disable the Firewall but no success.
I don't able to open the Configuration Manager. Somebody can help me?
Thanks.

OK, very good.
Just so I completely understand this ... On the Distributor AW, part of your Sprawler, can you use the Config Tool OK? If so, this means that the real-time feed is established to the Distributor and it can see the local database and so on.
Is the rtdist process running?
Now on the AW Client. Assuming this is configured correctly, it connects to the Distributor. Check the rtdist process to see your client AW IP address connect. Do you see this?
(I feel like we have discussed this before)
Regards,
Geoff

DAC has 19 inactive sessions in Repository Database

Similar Messages

Maybe you are looking for