Give all resources to a service/session/user
Hi,
I'm looking for a way to let one user/session/service consume all availabe database resources. A short overview over our system: We've got a primary three node RAC and a physical standby database running on the same host using a different storage subsystem. The standby is primarily used for reporting purposes (active dataguard). We've got a software running that produces highly complex queries. There are about 100 such "datawarehouse" queries running at the same time taking a lot of physical and logical I/O. The problem: Sometimes we receive queries that have highest priority and which must be completed as fast as possible. But as you can imagine there is no chance of getting a fast result when there are 100 other queries running in the background all of which consume lots of I/O.
When I first came to this problem I thought of using the Resource manager. I would create a consumer group, give it about 95% of the resources in every resource plan and map it to a specific service which then can be used to issue critical queries. But when I decided to set this up I came across the documentation which told me that the resource manager only cares about CPU. There is no way to give the session 100% of all availible I/O. Then I read a posting in a forum which told "If there is no CPU for a session it cannot issue I/O requests. So restricting CPU access also restricts I/O". Ok, great.. But the problem is: The critical session will NEVER consume all available CPU power. And because of the Resource managers philosophy that it will only take action when a resource is at it's limit there will never be an restriction on cpu power.
My second approach was to quiesce the database, but that seems to require the sysdba privilege, which I will never give to any software. So my question is: Is there any way to solve this problem?
Many thanks in advance
Thomas
Hi,
since your are using Active Data Guard, which means you are on 11g, you should take a closer look on DBRM new features - switching plan based on the number of IO requests and active session pool constraints. If I understand your requirements correctly, you can switch your sessions which took too many IO to the constrained consumer group (either automatically or manually) and for that group you can set maximum number of active sessions. In this case, sessions which uses IO and should be constrained can be reduced in their number, which, I think, should reduce their IO needs in total.
Similar Messages
-
Disable fading visual effect for all session users
Hello guys,
someone can say me how I can disable fading visual effect on windows 2012 R2 RDS?
All session users have these visual effect that I don't know how to disable.
Thanks
AndreaHi,
Thank you for posting in Windows Server Forum.
Firstly please try to provide TP’s reply, in addition to that you can check below settings on server and see the result.
You need to edit parts of System Properties-Performance Options as per below snap.
Snap:
For more information, refer beneath articles might help to solve your issue.
1. Disable visual effects in Windows
2. Program menus slow when accessed through Remote Desktop / Terminal Services
Hope it helps!
Thanks.
Dharmesh Solanki -
User can see all resources, not only Permitted for his/her Organization
Hi,
I have set three self-serviceable resources as Permitted Resources for a specific organization. So if I click on Permitted Resources for that organization I can see only those three...
When an user of that organization clicks on Request New Resources, all self-serviceable resources are listed to the user, not only the Permitted Resources. I thought the user could see only the permitted resources...
If I log as sys admin and Request Resources for an user of this organization, I can see only the three permitted resources.
I saw the sql statement that OIM run to list the resources:
select
obj.obj_key,obj_name,obj.sdk_key,sdk_name, obj_order_for,obj_auto_prepop, obj_type,
obj_allow_multiple, obj_self_request_allowed,obj_autosave,obj_allowall,
obj_rowver, obj_note,obj_autolaunch
from obj obj
left outer join sdk sdk on obj.sdk_key = sdk.sdk_key
where obj.obj_key in
select distinct obj.obj_key from obj obj
left outer join sdk sdk on obj.sdk_key = sdk.sdk_key
left outer join acp acp on obj.obj_key = acp.obj_key
left outer join oba oba on obj.obj_key = oba.obj_key
where
obj.obj_self_request_allowed='1' or obj.obj_key in
select obj_key from acp where act_key in
select act_key
from usr
where usr_key= 5 and acp_self_servicable = '1'
) and
obj.obj_order_for = 'U' and
(obj.obj_type='Application' or obj.obj_type='Generic') and
obj.obj_key not in
select pop.obj_key
from pop pop, pol pol, pog pog, ugp ugp, usg usg
where
pop.pol_key=pol.pol_key and
pol.pol_key=pog.pol_key and
pog.ugp_key=ugp.ugp_key and
ugp.ugp_key=usg.ugp_key and
usg.usr_key in (5) and
pop.pop_denial='1'
) and
obj.obj_key not in (
select distinct obj.obj_key
from obj obj, obi obi, ost ost, oiu oiu
left outer join orc orc on oiu.orc_key=orc.orc_key
where
oiu.obi_key=obi.obi_key and
oiu.ost_key=ost.ost_key and
upper(ost.ost_status) <> 'REVOKED' and
obi.obj_key=obj.obj_key and
oiu.usr_key in (5) and
obj.obj_allow_multiple='0'
) and
obj.obj_key in
select distinct obj_key
from pkg
where pkg_type='Provisioning'
As you can see in the query above, if I change the snippet below the result is what I expect.
obj.obj_self_request_allowed='1' AND obj.obj_key in
Did I miss to set something or doing something wrong?
Thanks,
Renato.Sorry, but I do not understand your last reply. You mentioned the following:
for option B, even when option A is unchecked, you can set self-request only for a specific organization when assign permitted resources.
Isnt this what you wanted? You should set the resource as permitted resources in all the organizations whose users can request that resource. I have implemented this and it works just fine. It works for both types of requests. a) My resources -> request new resources and b) Requests -> Resources -> Grant resources.
In case of b, depending on the organization to which the selected user belongs, the Resource is displayed. all resources are not displayed.
So the solution is to uncheck in RO and put the resource under specific organizations permitted resources and make it self-requestable. It should work fine. Let me know your exact issue if it does not work this way. -
Root. how to give all the privileges to user?
hi! im root and i want to give all the privileges to my user so he can open any program and any root folder. not in terminal (sudo gparted... for example) but i want to double click the program and open it. im using gnome. also i dont want to right click and open as admin. how can i do that?
thanksjowilkin wrote:
manolos wrote:
eldragon wrote:
no, no, no.....if you really want to do this...get a mac..
there are really good reasons for these limitations in user access..
if you want to stay away from the terminal, i think gksu should help you with that. (still need to type your password though)... if you dont like the terminal, maybe arch linux isnt the right distro for you, how about ubuntu?
its not a solution for me but thanks! ubuntu is very simple. i want to learn from linux... not just install!
Well, first lesson...what you want to do is a really bad idea.
hahaha! ill stay in terminal thanks for the advice! -
Cannot Install Sql Server 2008, Gives The Error "Database Engine Services Failed"
I cannot install Sql Server 2008 R2 on Windows 8. Tried many times but failed because it gives the error "Database
Engine Services Failed". Sql files cannot be corrupted because i can install the same setup on Windows 7 and i can connect to databases.
I tried all the things below;
* I'm uninstalling everything related with Sql Server from Control Panel/Programs And Features.
* I'm deleting all the keys related with Sql Server from Regedit.
* Later i'm restarting windows, and trying to install again. But during the install it gives the error "Database
Engine Services Failed", install is finishing but when i opened the Management Studio i cannot connect to Database Engine with Sa naturally.
* My firewall is already closed. And i have not any antivirus software.
* I gave the permission for port 1433 on firewall.
Please help me. Why i always take "Database Engine Services Failed" error? I will get crazy cause of that for many days.Here's the ERRORLOG file which i found under the folder;
Microsoft SQL Server/MSSQL10_50.MSSQLSERVER/MSSQL/Log.
2014-09-27 03:39:40.15 Server Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)
Apr 2 2010 15:48:46
Copyright (c) Microsoft Corporation
Developer Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
2014-09-27 03:39:40.15 Server (c) Microsoft Corporation.
2014-09-27 03:39:40.15 Server All rights reserved.
2014-09-27 03:39:40.15 Server Server process ID is 5768.
2014-09-27 03:39:40.15 Server System Manufacturer: 'SAMSUNG ELECTRONICS CO., LTD.', System Model: '350V5C/350V5X/350V4C/350V4X/351V5C/351V5X/351V4C/351V4X/3540VC/3540VX/3440VC/3440VX'.
2014-09-27 03:39:40.15 Server Authentication mode is MIXED.
2014-09-27 03:39:40.15 Server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2014-09-27 03:39:40.15 Server Registry startup parameters:
-d C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2014-09-27 03:39:40.15 Server Command Line Startup Parameters:
-m SqlSetup
-f
-Q
-q Turkish_CI_AS
-T 4022
-T 4010
-T 3659
-T 3610
2014-09-27 03:39:40.18 Server Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically. After
the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
2014-09-27 03:39:40.18 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-09-27 03:39:40.18 Server Detected 4 CPUs. This is an informational message; no user action is required.
2014-09-27 03:39:40.31 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2014-09-27 03:39:40.32 Server Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2014-09-27 03:39:40.43 Server Node configuration: node 0: CPU mask: 0x000000000000000f:0 Active CPU mask: 0x000000000000000f:0. This message provides a description of the NUMA configuration for this computer. This is an informational message
only. No user action is required.
2014-09-27 03:39:40.45 Server Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No user action
is required.
2014-09-27 03:39:40.45 spid7s Warning ******************
2014-09-27 03:39:40.45 spid7s SQL Server started in single-user mode. This an informational message only. No user action is required.
2014-09-27 03:39:40.46 spid7s Starting up database 'master'.
2014-09-27 03:39:40.52 spid7s Recovery is writing a checkpoint in database 'master' (1). This is an informational message only. No user action is required.
2014-09-27 03:39:40.58 spid7s SQL Server was started using the -f flag. SQL Server Audit is disabled. This is an informational message. No user action is required.
2014-09-27 03:39:40.59 spid7s FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:40.59 spid7s Server started with '-f' option. Auditing will not be started. This is an informational message only; no user action is required.
2014-09-27 03:39:40.59 spid7s Starting up database 'mssqlsystemresource'.
2014-09-27 03:39:40.61 spid7s The resource database build version is 10.50.1600. This is an informational message only. No user action is required.
2014-09-27 03:39:40.94 spid7s Password policy update was successful.
2014-09-27 03:39:40.94 spid8s Starting up database 'model'.
2014-09-27 03:39:40.95 spid7s Server name is 'CAGATAY'. This is an informational message only. No user action is required.
2014-09-27 03:39:41.21 spid8s Clearing tempdb database.
2014-09-27 03:39:41.21 spid10s A new instance of the full-text filter daemon host process has been successfully started.
2014-09-27 03:39:41.24 Server A self-generated certificate was successfully loaded for encryption.
2014-09-27 03:39:41.24 Server Server local connection provider is ready to accept connection on [ \\.\pipe\SQLLocal\MSSQLSERVER ].
2014-09-27 03:39:41.24 Server Dedicated administrator connection support was not started because it is disabled on this edition of SQL Server. If you want to use a dedicated administrator connection, restart SQL Server using the trace flag
7806. This is an informational message only. No user action is required.
2014-09-27 03:39:41.28 Server The SQL Server Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service. Error: 0x54b, state: 3. Failure to register an SPN may cause integrated authentication
to fall back to NTLM instead of Kerberos. This is an informational message. Further action is only required if Kerberos authentication is required by authentication policies.
2014-09-27 03:39:41.28 Server SQL Server is now ready for client connections. This is an informational message; no user action is required.
2014-09-27 03:39:41.70 spid8s Starting up database 'tempdb'.
2014-09-27 03:39:41.86 spid7s Warning ******************
2014-09-27 03:39:41.86 spid7s Attempting to change default collation to Turkish_CI_AS.
2014-09-27 03:39:41.92 spid7s index restored for master.syspriorities.
2014-09-27 03:39:41.95 spid7s index restored for master.sysbrickfiles.
2014-09-27 03:39:41.96 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:41.96 spid7s index restored for master.sysowners.
2014-09-27 03:39:42.13 spid7s index restored for master.sysdbreg.
2014-09-27 03:39:42.16 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.16 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.16 spid7s index restored for master.sysschobjs.
2014-09-27 03:39:42.17 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.17 spid7s index restored for master.syscolpars.
2014-09-27 03:39:42.17 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.sysxlgns.
2014-09-27 03:39:42.18 spid7s index restored for master.sysxsrvs.
2014-09-27 03:39:42.18 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.sysnsobjs.
2014-09-27 03:39:42.18 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.18 spid7s index restored for master.syscerts.
2014-09-27 03:39:42.19 spid7s index restored for master.sysrmtlgns.
2014-09-27 03:39:42.19 spid7s index restored for master.sysxprops.
2014-09-27 03:39:42.19 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.19 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.31 spid7s index restored for master.sysscalartypes.
2014-09-27 03:39:42.31 spid7s index restored for master.sysidxstats.
2014-09-27 03:39:42.31 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysendpts.
2014-09-27 03:39:42.32 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysclsobjs.
2014-09-27 03:39:42.32 spid7s index restored for master.sysremsvcbinds.
2014-09-27 03:39:42.32 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.32 spid7s index restored for master.sysrts.
2014-09-27 03:39:42.33 spid7s index restored for master.sysasymkeys.
2014-09-27 03:39:42.33 spid7s index restored for master.syssqlguides.
2014-09-27 03:39:42.44 spid7s index restored for master.syssoftobjrefs.
2014-09-27 03:39:42.47 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.48 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.49 spid7s index restored for master.spt_values.
2014-09-27 03:39:42.49 spid7s index restored for master.MSreplication_options.
2014-09-27 03:39:42.56 spid7s index restored for tempdb.syspriorities.
2014-09-27 03:39:42.56 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s index restored for tempdb.sysowners.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.57 spid7s index restored for tempdb.sysschobjs.
2014-09-27 03:39:42.57 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.59 spid7s index restored for tempdb.syscolpars.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysnsobjs.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.syscerts.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysxprops.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.60 spid7s index restored for tempdb.sysscalartypes.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysidxstats.
2014-09-27 03:39:42.61 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysclsobjs.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysremsvcbinds.
2014-09-27 03:39:42.61 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.61 spid7s index restored for tempdb.sysrts.
2014-09-27 03:39:42.62 spid7s index restored for tempdb.sysasymkeys.
2014-09-27 03:39:42.69 spid7s index restored for tempdb.syssqlguides.
2014-09-27 03:39:42.69 spid7s index restored for tempdb.syssoftobjrefs.
2014-09-27 03:39:42.75 spid7s index restored for model.syspriorities.
2014-09-27 03:39:42.75 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.75 spid7s index restored for model.sysowners.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:42.76 spid7s index restored for model.sysschobjs.
2014-09-27 03:39:42.76 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.syscolpars.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.sysnsobjs.
2014-09-27 03:39:43.00 spid7s index restored for model.syscerts.
2014-09-27 03:39:43.00 spid7s index restored for model.sysxprops.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.00 spid7s index restored for model.sysscalartypes.
2014-09-27 03:39:43.00 spid7s index restored for model.sysidxstats.
2014-09-27 03:39:43.01 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.01 spid7s index restored for model.sysclsobjs.
2014-09-27 03:39:43.01 spid7s index restored for model.sysremsvcbinds.
2014-09-27 03:39:43.01 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.01 spid7s index restored for model.sysrts.
2014-09-27 03:39:43.01 spid7s index restored for model.sysasymkeys.
2014-09-27 03:39:43.01 spid7s index restored for model.syssqlguides.
2014-09-27 03:39:43.01 spid7s index restored for model.syssoftobjrefs.
2014-09-27 03:39:43.02 spid7s Starting up database 'msdb'.
2014-09-27 03:39:43.82 spid7s index restored for msdb.syspriorities.
2014-09-27 03:39:43.85 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:43.93 spid7s index restored for msdb.sysowners.
2014-09-27 03:39:43.99 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.00 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.09 spid7s index restored for msdb.sysschobjs.
2014-09-27 03:39:44.12 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.20 spid7s index restored for msdb.syscolpars.
2014-09-27 03:39:44.20 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.20 spid7s index restored for msdb.sysnsobjs.
2014-09-27 03:39:44.20 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.25 spid7s index restored for msdb.syscerts.
2014-09-27 03:39:44.25 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.26 spid7s index restored for msdb.sysxprops.
2014-09-27 03:39:44.26 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.26 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.27 spid7s index restored for msdb.sysscalartypes.
2014-09-27 03:39:44.37 spid7s index restored for msdb.sysidxstats.
2014-09-27 03:39:44.41 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysclsobjs.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysremsvcbinds.
2014-09-27 03:39:44.42 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.42 spid7s index restored for msdb.sysrts.
2014-09-27 03:39:44.54 spid7s index restored for msdb.sysasymkeys.
2014-09-27 03:39:44.54 spid7s index restored for msdb.syssqlguides.
2014-09-27 03:39:44.59 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.74 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:44.85 spid7s index restored for msdb.syssoftobjrefs.
2014-09-27 03:39:44.89 spid7s index restored for msdb.syspolicy_policies_internal.
2014-09-27 03:39:44.90 spid7s index restored for msdb.sysproxies.
2014-09-27 03:39:44.90 spid7s index restored for msdb.syscollector_execution_stats_internal.
2014-09-27 03:39:44.90 spid7s index restored for msdb.syssubsystems.
2014-09-27 03:39:44.91 spid7s index restored for msdb.log_shipping_primary_secondaries.
2014-09-27 03:39:44.91 spid7s index restored for msdb.sysdownloadlist.
2014-09-27 03:39:44.91 spid7s index restored for msdb.log_shipping_monitor_primary.
2014-09-27 03:39:44.92 spid7s index restored for msdb.sysoriginatingservers.
2014-09-27 03:39:44.93 spid7s index restored for msdb.log_shipping_monitor_history_detail.
2014-09-27 03:39:44.95 spid7s index restored for msdb.log_shipping_monitor_error_detail.
2014-09-27 03:39:44.95 spid7s index restored for msdb.log_shipping_secondary.
2014-09-27 03:39:44.97 spid7s index restored for msdb.log_shipping_secondary_databases.
2014-09-27 03:39:45.10 spid7s index restored for msdb.log_shipping_monitor_secondary.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysjobs.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysutility_ucp_mi_file_space_health_internal.
2014-09-27 03:39:45.10 spid7s index restored for msdb.sysutility_ucp_mi_database_health_internal.
2014-09-27 03:39:45.10 spid7s index restored for msdb.syscollector_blobs_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_mi_dac_execution_statistics_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysjobsteps.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_ucp_dac_file_space_health_internal.
2014-09-27 03:39:45.11 spid7s index restored for msdb.logmarkhistory.
2014-09-27 03:39:45.11 spid7s index restored for msdb.sysutility_mi_session_statistics_internal.
2014-09-27 03:39:45.12 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.12 spid7s index restored for msdb.sysdtscategories.
2014-09-27 03:39:45.33 spid7s index restored for msdb.syspolicy_target_sets_internal.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysutility_ucp_mi_volume_space_health_internal.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysschedules.
2014-09-27 03:39:45.33 spid7s index restored for msdb.sysdac_instances_internal.
2014-09-27 03:39:45.33 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.50 spid7s index restored for msdb.sysssispackages.
2014-09-27 03:39:45.51 spid7s index restored for msdb.sysutility_ucp_computer_cpu_health_internal.
2014-09-27 03:39:45.51 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.52 spid7s index restored for msdb.sysssispackagefolders.
2014-09-27 03:39:45.52 spid7s index restored for msdb.sysdac_history_internal.
2014-09-27 03:39:45.53 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.62 spid7s index restored for msdb.syscategories.
2014-09-27 03:39:45.62 spid7s index restored for msdb.systargetservers.
2014-09-27 03:39:45.62 spid7s index restored for msdb.systargetservergroups.
2014-09-27 03:39:45.62 spid7s index restored for msdb.syspolicy_policy_category_subscriptions_internal.
2014-09-27 03:39:45.62 spid7s index restored for msdb.sysalerts.
2014-09-27 03:39:45.62 spid7s index restored for msdb.sysoperators.
2014-09-27 03:39:45.63 spid7s index restored for msdb.syspolicy_system_health_state_internal.
2014-09-27 03:39:45.63 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.63 spid7s index restored for msdb.syscollector_config_store_internal.
2014-09-27 03:39:45.65 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.65 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.65 spid7s index restored for msdb.sysmanagement_shared_server_groups_internal.
2014-09-27 03:39:45.66 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.66 spid7s index restored for msdb.sysutility_mi_smo_properties_to_collect_internal.
2014-09-27 03:39:45.66 spid7s index restored for msdb.sysmanagement_shared_registered_servers_internal.
2014-09-27 03:39:45.66 spid7s index restored for msdb.syscachedcredentials.
2014-09-27 03:39:45.79 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.79 spid7s index restored for msdb.syscollector_collection_sets_internal.
2014-09-27 03:39:45.79 spid7s index restored for msdb.sysutility_ucp_dac_health_internal.
2014-09-27 03:39:45.80 spid7s index restored for msdb.MSdbms.
2014-09-27 03:39:45.80 spid7s index restored for msdb.MSdbms_datatype.
2014-09-27 03:39:45.80 spid7s index restored for msdb.sysmail_profile.
2014-09-27 03:39:45.80 spid7s index restored for msdb.sysutility_ucp_managed_instances_internal.
2014-09-27 03:39:45.83 spid7s index restored for msdb.syspolicy_management_facets.
2014-09-27 03:39:45.84 spid7s index restored for msdb.sysutility_ucp_mi_health_internal.
2014-09-27 03:39:45.86 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.86 spid7s index restored for msdb.syscollector_collector_types_internal.
2014-09-27 03:39:45.86 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.86 spid7s index restored for msdb.syspolicy_configuration_internal.
2014-09-27 03:39:45.87 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.87 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.87 spid7s index restored for msdb.syspolicy_facet_events.
2014-09-27 03:39:45.87 spid7s index restored for msdb.sysmail_account.
2014-09-27 03:39:45.87 spid7s index restored for msdb.syspolicy_conditions_internal.
2014-09-27 03:39:45.88 spid7s index restored for msdb.sysutility_ucp_health_policies_internal.
2014-09-27 03:39:45.88 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:45.88 spid7s index restored for msdb.syscollector_collection_items_internal.
2014-09-27 03:39:45.90 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.00 spid7s index restored for msdb.sysmail_servertype.
2014-09-27 03:39:46.00 spid7s index restored for msdb.sysutility_ucp_filegroups_with_policy_violations_internal.
2014-09-27 03:39:46.02 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_policy_check_conditions_internal.
2014-09-27 03:39:46.03 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_configuration_internal.
2014-09-27 03:39:46.03 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.03 spid7s index restored for msdb.sysutility_ucp_policy_target_conditions_internal.
2014-09-27 03:39:46.04 spid7s index restored for msdb.sysmail_server.
2014-09-27 03:39:46.04 spid7s index restored for msdb.syspolicy_policy_categories_internal.
2014-09-27 03:39:46.04 spid7s index restored for msdb.syspolicy_object_sets_internal.
2014-09-27 03:39:46.04 spid7s Index creation operation will use 1024 KB of memory specified in the advanced sp_configure option "min memory per query (KB)" instead of 704 KB specified in "index create memory (KB)" option
because the former has to be smaller than the latter.
2014-09-27 03:39:46.05 spid7s index restored for msdb.sysmail_configuration.
2014-09-27 03:39:46.05 spid7s index restored for msdb.sysdbmaintplan_databases.
2014-09-27 03:39:46.05 spid7s index restored for msdb.log_shipping_primary_databases.
2014-09-27 03:39:46.39 spid7s The default collation was successfully changed.
2014-09-27 03:39:46.39 spid7s Recovery is complete. This is an informational message only. No user action is required.
2014-09-27 03:39:47.17 spid51 Changed database context to 'master'.
2014-09-27 03:39:47.18 spid51 Changed language setting to us_english.
2014-09-27 03:39:47.72 spid51 Setting database option RECOVERY to FULL for database model.
2014-09-27 03:39:47.84 spid51 Configuration option 'show advanced options' changed from 0 to 1. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.84 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:47.98 spid51 Configuration option 'default language' changed from 0 to 0. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 Configuration option 'default full-text language' changed from 1033 to 1033. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:47.98 spid51 Configuration option 'show advanced options' changed from 1 to 0. Run the RECONFIGURE statement to install.
2014-09-27 03:39:47.98 spid51 FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'MSSQLSERVER'.
2014-09-27 03:39:48.27 spid51 Error: 15007, Severity: 16, State: 1.
2014-09-27 03:39:48.27 spid51 '' is not a valid login or you do not have permission.
2014-09-27 03:51:25.13 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:51:25.13 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:51:32.67 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:51:32.67 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:51:42.11 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:51:42.11 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:52:42.07 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:52:42.07 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:53:01.23 Logon Error: 18461, Severity: 14, State: 1.
2014-09-27 03:53:01.23 Logon Login failed for user 'CAGATAY\cagatay'. Reason: Server is in single user mode. Only one administrator can connect at this time. [CLIENT: <local machine>]
2014-09-27 03:53:17.57 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:53:17.57 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
2014-09-27 03:53:32.54 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:53:32.54 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:04.29 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:54:04.29 Logon Login failed for user 'CAGATAY\cagatay (cagatay)'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:10.36 Logon Error: 18456, Severity: 14, State: 5.
2014-09-27 03:54:10.36 Logon Login failed for user 'CAGATAY\cagatay'. Reason: Could not find a login matching the name provided. [CLIENT: <local machine>]
2014-09-27 03:54:47.18 Logon Error: 18456, Severity: 14, State: 8.
2014-09-27 03:54:47.18 Logon Login failed for user 'sa'. Reason: Password did not match that for the login provided. [CLIENT: <local machine>]
Resolve the error, please refer to the following links.
Enable DAC:http://www.mssqltips.com/sqlservertip/2538/enabling-dedicated-administrator-connection-in-sql-server-2008-express-edition/
could not register the SPN Kerberos:
http://saveadba.blogspot.com/2012/03/could-not-register-spn-kerberos.html
Make sure the password of sa is correct,and the login 'CAGATAY\cagatay' has been created in SQL Server -
Hi Experts,
I want my service desk users login on Solman and they can update Msg status and ther remarks.
so what are auth. object needs on there profile, please suggest.
Can we block users access in such a way , they are not able to do add change on other users issue msg.
bcoz , if i give access on crm_dno_monitor to any user, he may access and process all issue tickets.
Thanks
AndrewAndree,
Actually we provide variants for crm_dno_monitor.
so they have option of seeing only tickets belonging to themselves only
For e.g create a variant of crm_dno_monitor by choosing mine and then save it and create a ztcode in se93 for the same.
assign this tcode for the user menu to the respective role of the user.
So whn this user logs in and click on the link he sees only mine tickets or tickets belonging to him..he doesnt hav access to crm_dno_monitor.
Pls assign pts. -
Interactive report gives an error only for a specific user
An interactive report based on a very complicated select gives an error only when a specific user is logged on.
The error is:
ORA-00932: inconsistent datatypes: expected - got CLOB.
For other users logging using this page it works fine.
Authentication for this application is done using a stored function.
The query does not use the current userid in it.
Why does it fail for a specific user? if there is a problem, it should fail all the time.Hi ankur,
By what you said the report dont have any date parameters or no date columns.
"Query execution was not successful ORA-01843 not a valid month." This means it is related with date mask passing a invalid month into date column or argument to to_date function.Check once the session date that is 'dd-mm-yy' or anything else
select * from nls_session_parameters where parameter = 'NLS_DATE_FORMAT'
select to_date('01-DEC-06'),to_date('01-12-06') from dual;
Also a general question whenever I am trying to mark any question as 'Helpful', the status is not changing. Is there anything I am missing.While you flag it 'helpful' or 'correct',it takes you to other screen where you see "Yes, the question is now answered" click the radio button and then click ok button.
Hope its helpful.
Best Wishes,
Kranthi.
Edited by: Kranthi.K on Jun 8, 2009 9:00 AM -
Inactive status - v$session users list over WEB application
Hi all
When user connect through asp or asp.net, we create a connection in the session object. New sid gets created with each session.
When user normally logs out the application, his sid gets finished in the v$session users list. But when he dees not logs out in the normal way as we can not force thousand of users over WEB to log out normally, what will happen to the v$session ?.
1st - We wish to know to know that whether the list will run into thousands of inactive status users OR they automatically gets finished over time. We use the default profile as applicable to new user.
2nd - If the list of inactive status users gets increased to thousands of users which can be possible for the WEB application , there must be some limit fixed by Oracle 8i/ 10g database OR there may be serious performance problems. This simultaneous connection of thousands of users over WEB is easily possible and when connection is created in session object , what could be the scenario. We avoid creating connection object in the application start event to improve performance for the given sesion.
Any help is appreciated.
Suresh bansalThanks for prompt reply
1st - Can u give some idea for create connection pools using asp.net environments. Further in the connection pool environment as to how much simultaneous running connections we should need to open and how.
2nd - If we have pool of say 100 connections and there are more number of simultaneous WEB users, what will happen to the application as to whether it gets to hanging /waiting for the pool connection to be free or give error ?.
Suresh Bansal -
I am new to Service module,can anybody give the over view of service module
I am new to Service module,can anybody give the over view of service module including base table and Relation ship with other Oracle Application module.
Hello Les,
Think that you want to buy television or computer and how will you proceed for that.
1. Material Requirement : Your family will ask you that they need television so that is material requirement from the users (family), they will also give additional information like what is the size of TV, which brand etc
2. Quotation (Inquiry) : now you have requirement that you need one TV so you will looking for different vendors i.e. Phillips, Sharp, AIWA, Deawood and ask them to give the prices and other terms (free shipping, service after sales ) for TV
3. Quotation comparision : Once you get the price from all your supplier, you will make comparision on price and other terms also you can negotiate the price with vendor asking for discounts, free door delivery
4. Vendor Selection: Based on your negotiation you will identify the best deal and place order to that vendor.
5. Purchase order : You will place order to vendor asking for material (TV), for certain price on particular date at particular location (you home).
6. Goods Receipt : Once vendor delivers TV then you will receive the material at your location
7. Invoice receipt: Vendor will send the invoice with that delivery and you will check the price and make the payment to vendor,
I hope this will help you to under stand the concept of Procurment cylce.
More details you can get it from the link which I provided.
Regards
Arif Mansuri -
Keeping "CS Web Service session" alive while uploading big files.
Hi.
I have a problem when I'm uploading big files, which takes longer than the session timeout value, causing the upload to fail.
As you all know uploading a file is a three step process:
1). Create a new DocumentDefinition Item on the server as a placeholder.
2). Open an HTTP connection to the created placeholder and transfer the data using the HTTPConnection.put() method.
3). Create the final document using the FileManager by passing in the destination folder and the document definition.
The problem is that step 2 take so long that the "CS Web Service Session" times out and thus step 3 can not be completed. The Developer guide gives a utility method for creating an HTTP connection for step 2 and it states the folllowing "..you must create a cookie for the given domain and path in order to keep the session alive while transferring data." But this only keeps the session of the HTTP Connection alive and not the "CS Web Service Session". As in my case step 2 completes succesfully and the moment I peform step 3 it throws an ORACLE.FDK.SessionError:ORACLE.FDK.SessionNotConnected exception.
How does one keep the "CS Web Service Session" alive?
Thanks in advance
Regards.Okay, even a thread that pushes dummy stuff through once in a while doesn't help. I'm getting the following when the keep alive thread kicks in while uploading a big file.
"AxisFault
faultCode: {http://xml.apache.org/axis/}HTTP
faultSubcode:
faultString: (409)Conflict
faultActor:
faultNode:
faultDetail:
{}:return code: 409
<HTML><HEAD><TITLE>409 Conflict</TITLE></HEAD><BODY><H1>409 Conflict</H1>Concurrent Requests On The Same Session Not Supported</BODY></HTML>
{http://xml.apache.org/axis/}HttpErrorCode:409
(409)Conflict
at org.apache.axis.transport.http.HTTPSender.readFromSocket(HTTPSender.java:732)
at org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:143)
at org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
at org.apache.axis.client.Call.invokeEngine(Call.java:2765)
at org.apache.axis.client.Call.invoke(Call.java:2748)
at org.apache.axis.client.Call.invoke(Call.java:2424)
at org.apache.axis.client.Call.invoke(Call.java:2347)
at org.apache.axis.client.Call.invoke(Call.java:1804)
at oracle.ifs.fdk.FileManagerSoapBindingStub.existsRelative(FileManagerSoapBindingStub.java:1138)"
I don't understand this, as the exception talks about "Concurrent Requests On The Same Session", but if their is already a request going on why is the session timing out in the first place?!
I must be doing something really stupid somewhere. Aia ajay jay what a unproductive day...
Any help? It will be greatly appreciated... -
Business rules for check current date and session user
MDS 2012
Hi All! How to make validation business rules:
1. date < GETDATE()
2. current session user is UserName(), where UserName() - system function like in MS Analysis Services
from Moscow with LoveThere is no way to create this with a Business Rule, you have to write a custom workflow or SQL nightly job or something to update your fields.
Ok people start screaming.
"solution" if you want to call it that. USE AT YOUR OWN RISK, try in dev first :)
1. Create an Attribute / Column in your Entity and call it Today or something.
2. Go to Business Rules and create a dummy rule where you are setting this attribute (unconditionally with no Condition)
Today equals 1/1/2000 or something.
3. Go to tblBRItem find this BR and etin ItemSQL from N'1/1/2000' to GETDATE()
now you have Todays Date field...
OK NEVER MIND, I've tried it and it works, the problem is that tblBRItems gets updated via a stored proc and will overwrite your entry.
One can modify the code there as well but I don't have time to play with it unfortunately, as at that time you have to pass some token in to identify some values as your own special commands ... Either way this becomes messy and not a way to go. -
How to make an user into Service authenticated user like cmadmin_service
Hi All,
I am trying to fetch the list of documents, properties, log on/logoff functionality with an iUser ex: epuser, through java code.
The list of docs are presented in the Documents Folder with teh following sample code
|
RID rid = RID.getRID("/documents");
String userName = "epuser";
IUserFactory userFactory = UMFactory.getUserFactory();
com.sap.security.api.IUser userNew;
userNew = userFactory.getUser(userName);
com.sapportals.portal.security.usermanagement.IUser user = WPUMFactory.getUserFactory().getEP5User(userNew);
ctx.setUser(user);
IResource res = null;
res = ResourceFactory.getInstance().getResource(rid, ctx);
wnen i am trying to fetch all the docs and the corresponding properties by passing " cmadmin_service " as an user name. i am getting the right results. But when i tried with "epuser " i am getting the output as Service Authentication value false.
Then i added epuser in the System Principal--->System User. still i am not getting the right results.
plz help me how to make this epuser as service authenticated user like cmadmin_service userHi phani,
I have no direct solution but you should check the service permissions of the resources you are trying to fetch. The exception sounds like there is the problem. Go to the Details of the CM-Resource and Select Settings-->Service Permissions.
Does the epuser has the necessary permissions for your operations?
Another thing is the way you are creating users:
The WPUMFactory has a special factory-method for creating service users. Perhaps this is a better aproach:
WPUMFactory.getServiceUserFactory().getServiceUser(user);
Best regards,
Stefan Brauneis -
Your Remote Desktop Services Session Has Ended - Occurs when running in background
Our remote desktop users are having an issues with the RD session ending whenever we are running it in the background. Namely the session will run as long as the computer is idle or I am actively working in RD. Within 4 minutes of leaving RD and working
in another application, I receive the message: Your Remote Desktop Services Session Has EndedYou are posting in the wrong forum. Post in the RDS forum for help with the RDS product.
¯\_(ツ)_/¯
Direct link:
https://social.technet.microsoft.com/Forums/en-us/home?forum=winserverTS%2CwinRDc&filter=alltypes&sort=lastpostdesc
Don't retire TechNet! -
(Don't give up yet - 13,085+ strong and growing) -
Remote Desktop Session - users presented with Other User only?
Hi,
I am running a 2008 R2 server patched up to date. It has the remote desktop services role installed. Whenever I RDP or if a user launches a terminal services session they are presented with OTHER USER only.
This involves clicking the Other User before entering their credentials which is becoming a pain.
Non of the other servers are behaving this way. I've compared the settings with the other and all is identical. I've checked the local security policy and disabled all Group Policies but the behaviour still persists. Any ideas?
Thanks, Matt.Hi Matt,
Can you clarify more for this line, “Whenever I RDP or if a user launches a terminal services session they are presented with OTHER USER only.” what you mean by this? If I understand, when you taking RDP, you need to enter the credential for user manually
and that you don’t want, yes? If misunderstood, please correct.
For that, for a try you can enable the Group policy under credential manager and enable SSO for remote desktop connection. You can find the setting under beneath path.
Computer Configuration\Administrative Templates\System\Credentials Delegation
Allow Delegating Default Credentials: Enable
Add "TERMSRV/<Your server name>" to the server list.
There are other setting which you can check with following link.
How to enable Single Sign-On for my Terminal Server connections
http://blogs.msdn.com/b/rds/archive/2007/04/19/how-to-enable-single-sign-on-for-my-terminal-server-connections.aspx
Hope it helps!
Thanks.
Dharmesh Solanki
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected] -
For all of you having services failing to start
After 48 hours of struggle with this same issue and 6 clean re-installs of Lion Server I have found the bug in Lion Server causing all ruby based collaboration services (Device Manager, Wiki, ical, some adress book features ie: major screw up in services around server admin tools and server app). The most visible one is in Profile Manager because as you all pointed out it even says sometimes "Error Reading Settings". And if you take a look at the logs its even worst...full of errors...
that's how I found out, yes reading all the logs took time:
Basically they all fail because they use Postgresql database.
At first I did 2 clean re-installs and noticed everytime, after having spent some time configuring the server (open directory/kerneros, creating accounts/mailboxes, profiles etc.). I would do a reboot and everything would break.
Now I won't go over all the diggin I did but I finally manage to understand why Postgres at some point was failing.
it seems there is a bug.
If you turn "Dedicate Resources to Server Services" in the Server.app Hardware Section (next to Push Notifications switch", postgres doesn't start and all depending services (lots) fail.
The Solution: Just turn that OFF as shown below and restart. Everything should get back in order. If you still see some "push_notify: not connected" erros in you console logs (it happened to me even thoug all servcies were restored) the solution is easy. Hit change and redo the setup with you appleid. You'll be issued new certs by Apple and everything shoudl work fine.
That's all.
Hope this helps the many people that are frustrated like I was. Now that everything works, it's the perfect server for a mini Cloud. You'll love Profile Manager for provisioning payload to your devices. Elegant, efficient and simple, yet very flexible with the openDirectory backend.
Cheers everyone !
Eric
twitter: @teknologismThe relevant logs (at the time of the failure loop):
PostgreSQL.log @ 2:43 I reboot the server and that's what we have after reboot...
2011-07-25 02:43:07 CEST LOG: database system is shut down
2011-07-25 02:54:00 CEST LOG: database system was shut down at 2011-07-25 02:43:07 CEST
2011-07-25 02:54:00 CEST LOG: autovacuum launcher started
2011-07-25 02:54:00 CEST LOG: database system is ready to accept connections
2011-07-25 02:54:03 CEST LOG: connection received: host=[local]
2011-07-25 02:54:03 CEST LOG: connection authorized: user=collab database=collab
2011-07-25 02:54:05 CEST LOG: connection received: host=[local]
2011-07-25 02:54:05 CEST LOG: connection authorized: user=collab database=collab
2011-07-25 02:54:05 CEST ERROR: duplicate key value violates unique constraint "global_settings_pkey"
2011-07-25 02:54:05 CEST DETAIL: Key (key)=(com.apple.setting.schema_version) already exists.
2011-07-25 02:54:05 CEST STATEMENT: INSERT INTO global_settings (key, value_int) VALUES ('com.apple.setting.schema_version', $1)
2011-07-25 02:54:05 CEST LOG: unexpected EOF on client connection
2011-07-25 02:54:05 CEST LOG: connection received: host=[local]
2011-07-25 02:54:05 CEST LOG: connection authorized: user=collab database=collab
2011-07-25 02:54:05 CEST LOG: connection received: host=[local]
2011-07-25 02:54:05 CEST LOG: connection authorized: user=collab database=collab
2011-07-25 02:55:21 CEST LOG: connection received: host=[local]
2011-07-25 02:55:21 CEST LOG: connection authorized: user=_postgres database=postgres
2011-07-25 02:55:22 CEST LOG: unexpected EOF on client connection
2011-07-25 02:55:22 CEST LOG: unexpected EOF on client connection
2011-07-25 02:55:22 CEST LOG: received smart shutdown request
2011-07-25 02:55:22 CEST LOG: autovacuum launcher shutting down
2011-07-25 02:55:22 CEST LOG: shutting down
2011-07-25 02:55:22 CEST LOG: database system is shut down
And that is the relevant part in the system.log:
Jul 25 02:43:01 teknologism org.clamav.freshclam[608]: ClamAV update process started at Mon Jul 25 02:43:01 2011
Jul 25 02:43:01 teknologism freshclam[608]: Your ClamAV installation is OUTDATED!
Jul 25 02:43:01 teknologism freshclam[608]: Local version: 0.97 Recommended version: 0.97.1
Jul 25 02:43:01 teknologism org.clamav.freshclam[608]: WARNING: Your ClamAV installation is OUTDATED!
Jul 25 02:43:01 teknologism org.clamav.freshclam[608]: WARNING: Local version: 0.97 Recommended version: 0.97.1
Jul 25 02:43:01 teknologism org.clamav.freshclam[608]: DON'T PANIC! Read http://www.clamav.net/support/faq
Jul 25 02:43:01 teknologism org.clamav.freshclam[608]: main.cvd is up to date (version: 53, sigs: 846214, f-level: 53, builder: sven)
Jul 25 02:43:01 teknologism org.clamav.freshclam[608]: daily.cld is up to date (version: 13356, sigs: 161751, f-level: 60, builder: ccordes)
Jul 25 02:43:02 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 4 seconds
Jul 25 02:43:07 teknologism servermgrd[118]: servermgr_postgres: killing idle postgres process with signature "postgres: _devicemgr device_management [local] idle", pid=596
Jul 25 02:43:07 teknologism servermgrd[118]: servermgr_postgres: killing idle postgres process with signature "postgres: _devicemgr device_management [local] idle", pid=595
Jul 25 02:43:07 teknologism servermgrd[118]: servermgr_postgres: killing idle postgres process with signature "postgres: _devicemgr device_management [local] idle", pid=594
Jul 25 02:43:07 teknologism servermgrd[118]: servermgr_postgres: killing idle postgres process with signature "postgres: _devicemgr device_management [local] idle", pid=593
Jul 25 02:43:07 teknologism servermgrd[118]: servermgr_postgres: killing idle postgres process with signature "postgres: _devicemgr device_management [local] idle", pid=592
Jul 25 02:43:07 teknologism servermgrd[118]: servermgr_postgres: killing idle postgres process with signature "postgres: _devicemgr device_management [local] idle", pid=591
Jul 25 02:43:07 teknologism servermgrd[118]: servermgr_postgres: killing idle postgres process with signature "postgres: _devicemgr device_management [local] idle", pid=590
Jul 25 02:43:07 teknologism servermgrd[118]: servermgr_postgres: killing idle postgres process with signature "postgres: _devicemgr device_management [local] idle", pid=589
Jul 25 02:43:07 teknologism servermgrd[118]: servermgr_postgres: killing idle postgres process with signature "postgres: _devicemgr device_management [local] idle", pid=588
Jul 25 02:43:07 teknologism servermgrd[118]: servermgr_postgres: killing idle postgres process with signature "postgres: _devicemgr device_management [local] idle", pid=587
Jul 25 02:43:07 teknologism servermgrd[118]: servermgr_postgres: killing idle postgres process with signature "postgres: caldav caldav [local] idle", pid=370
Jul 25 02:43:10 teknologism servermgrd[118]: servermgr_ipfilter:ipfw config:Notice:Flushed IPv4 rules
Jul 25 02:43:10 teknologism servermgrd[118]: servermgr_ipfilter:ipfw config:Notice:Flushed IPv6 rules
Jul 25 02:43:11 teknologism com.apple.collabd.podcast-cache-updater[640]: /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put': Couldn't connect to server (Curl::Err::ConnectionFailedError)
Jul 25 02:43:11 teknologism com.apple.collabd.podcast-cache-updater[640]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put'
Jul 25 02:43:11 teknologism com.apple.collabd.podcast-cache-updater[640]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:102:in `sendRequest'
Jul 25 02:43:11 teknologism com.apple.collabd.podcast-cache-updater[640]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:153:in `execute'
Jul 25 02:43:11 teknologism com.apple.collabd.podcast-cache-updater[640]: from /usr/share/collabd/server/ruby/../../coreclient/vendor/plugins/podcasts/app/hel pers/podcast_cache_util.rb:23:in `initialize'
Jul 25 02:43:11 teknologism com.apple.collabd.podcast-cache-updater[640]: from /usr/share/collabd/server/ruby/podcast_cache_updater.rb:24:in `new'
Jul 25 02:43:11 teknologism com.apple.collabd.podcast-cache-updater[640]: from /usr/share/collabd/server/ruby/podcast_cache_updater.rb:24
Jul 25 02:43:11 teknologism com.apple.launchd[1] (com.apple.collabd.podcast-cache-updater[640]): Exited with code: 1
Jul 25 02:43:13 teknologism servermgrd[118]: servermgr_postgres: waiting for postgres to respond
Jul 25 02:43:13 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 3 seconds
Jul 25 02:43:14 teknologism servermgrd[118]: servermgr_postgres: waiting for postgres to respond
Jul 25 02:43:15: --- last message repeated 2 times ---
Jul 25 02:43:15 teknologism servermgrd[118]: servermgr_postgres: Timed out trying to start postgres.
Jul 25 02:43:17 teknologism mdworker[660]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 132970 swapped: 2 regions: 413), hit usage threshold importing /private/var/db/swupd/html/content/downloads/39/44/041-1233/K2dbQDWBvBwvYXpkr5v 3qkvMvqYGq3Y94D/AlKybdFirmwareUpdate.smd.previous, exiting to clean up.
Jul 25 02:43:19 teknologism servermgrd[118]: servermgr_devicemgr: prepareForOffline: error db:migrate: 1
Jul 25 02:43:19 teknologism pcastwatcher[479]: Cluster member role changed to LEADER
Jul 25 02:43:21 teknologism servermgrd[118]: servermgr_postgres: waiting for postgres to respond
Jul 25 02:43:22 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 5 seconds
Jul 25 02:43:22 teknologism servermgrd[118]: servermgr_postgres: waiting for postgres to respond
Jul 25 02:43:23: --- last message repeated 2 times ---
Jul 25 02:43:23 teknologism servermgrd[118]: servermgr_postgres: Timed out trying to start postgres.
Jul 25 02:43:27 teknologism mdworker[674]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 134078 swapped: 2 regions: 413), hit usage threshold importing /private/var/db/swupd/html/content/downloads/16/52/061-3533/rMnHGtg5jbQBVQFSLzH WnNdVRmZNWgcM3Q/MacBookProEFIUpdate1.3.smd.previous, exiting to clean up.
Jul 25 02:43:27 teknologism servermgrd[118]: servermgr_devicemgr: prepareForOffline: error db:migrate: 1
Jul 25 02:43:32 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 5 seconds
Jul 25 02:43:37 teknologism mdworker[678]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 130851 swapped: 2 regions: 413), hit usage threshold importing /private/var/db/swupd/html/content/downloads/40/21/061-5964/S27D5FnWT54LZjFmRFb N46dSTSYhxy8QyG/MacBookSMCUpdate.smd.previous, exiting to clean up.
Jul 25 02:43:42 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 5 seconds
Jul 25 02:43:47 teknologism mdworker[296]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 132280 swapped: 2 regions: 417), hit usage threshold importing /Users/teknologist/Library/Saved Application State/com.apple.Console.savedState/windows.plist, exiting to clean up.
Jul 25 02:43:52 teknologism mdworker[683]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 132244 swapped: 2 regions: 412), hit usage threshold importing /private/var/db/swupd/html/content/downloads/42/28/061-5258/Nhf7yJ5zHRDgGqW3CrN WPQYvTSxLMykkgP/HP_PrinterSupport.smd, exiting to clean up.
Jul 25 02:43:58 teknologism mdworker[691]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 131620 swapped: 2 regions: 413), hit usage threshold importing /private/var/pgsql/base/16389/17282, exiting to clean up.
Jul 25 02:44:03 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 5 seconds
Jul 25 02:44:08 teknologism mdworker[695]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 131245 swapped: 2 regions: 413), hit usage threshold importing /private/var/db/swupd/html/content/downloads/63/62/061-3767/swJZDhd67fxx4fY4Pkk QHNvxhQvF6vgyqz/CinemaToolsUpdate4.0.1.smd.previous, exiting to clean up.
Jul 25 02:44:13 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 5 seconds
Jul 25 02:44:18 teknologism mdworker[699]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 131620 swapped: 2 regions: 413), hit usage threshold importing /private/var/db/swupd/html/content/downloads/16/19/061-3508/LQHLx2HjZkYbPnvsTJZ G9DFP5hLzRqmmG3/FrontRowUpdate1.3.1.smd.previous, exiting to clean up.
Jul 25 02:44:23 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 5 seconds
Jul 25 02:44:24 teknologism serveradmin[704]: servermgr_postgres: waiting for postgres to respond
Jul 25 02:44:26: --- last message repeated 3 times ---
Jul 25 02:44:26 teknologism serveradmin[704]: servermgr_postgres: Timed out trying to start postgres.
Jul 25 02:44:26 teknologism serveradmin[704]: posting dist not
Jul 25 02:44:26 teknologism com.apple.collabd.notifications[154]: /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put': Couldn't connect to server (Curl::Err::ConnectionFailedError)
Jul 25 02:44:26 teknologism com.apple.collabd.notifications[154]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put'
Jul 25 02:44:26 teknologism com.apple.collabd.notifications[154]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:102:in `sendRequest'
Jul 25 02:44:26 teknologism com.apple.collabd.notifications[154]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:153:in `execute'
Jul 25 02:44:26 teknologism com.apple.collabd.notifications[154]: from notifications.rb:145:in `initialize'
Jul 25 02:44:26 teknologism com.apple.collabd.notifications[154]: from notifications.rb:439:in `new'
Jul 25 02:44:26 teknologism com.apple.collabd.notifications[154]: from notifications.rb:439
Jul 25 02:44:26 teknologism com.apple.launchd[1] (com.apple.collabd.notifications[154]): Exited with code: 1
Jul 25 02:44:28 teknologism postfix/smtpd[716]: warning: unknown[192.168.176.150]: SASL CRAM-MD5 authentication failed
Jul 25 02:44:28 teknologism com.apple.collabd.notifications[709]: /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put': Couldn't connect to server (Curl::Err::ConnectionFailedError)
Jul 25 02:44:28 teknologism com.apple.collabd.notifications[709]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put'
Jul 25 02:44:28 teknologism com.apple.collabd.notifications[709]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:102:in `sendRequest'
Jul 25 02:44:28 teknologism com.apple.collabd.notifications[709]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:153:in `execute'
Jul 25 02:44:28 teknologism com.apple.collabd.notifications[709]: from notifications.rb:145:in `initialize'
Jul 25 02:44:28 teknologism com.apple.collabd.notifications[709]: from notifications.rb:439:in `new'
Jul 25 02:44:28 teknologism com.apple.collabd.notifications[709]: from notifications.rb:439
Jul 25 02:44:28 teknologism com.apple.launchd[1] (com.apple.collabd.notifications[709]): Exited with code: 1
Jul 25 02:44:28 teknologism com.apple.launchd[1] (com.apple.collabd.notifications): Throttling respawn: Will start in 9 seconds
Jul 25 02:44:28 teknologism mdworker[729]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 136258 swapped: 2 regions: 414), hit usage threshold importing /private/var/db/swupd/html/content/downloads/46/49/061-4414/KfF9HYN5nxHSkVvYhqf 9JTW3kFs6R3bmgr/MacProGraphicsFWUpdate.smd.previous, exiting to clean up.
Jul 25 02:44:33 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 5 seconds
Jul 25 02:44:38 teknologism com.apple.collabd.notifications[732]: /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put'
Jul 25 02:44:38 teknologism com.apple.collabd.notifications[732]: : Couldn't connect to server (Curl::Err::ConnectionFailedError)
Jul 25 02:44:38 teknologism com.apple.collabd.notifications[732]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put'
Jul 25 02:44:38 teknologism com.apple.collabd.notifications[732]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:102:in `sendRequest'
Jul 25 02:44:38 teknologism com.apple.collabd.notifications[732]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:153:in `execute'
Jul 25 02:44:38 teknologism com.apple.collabd.notifications[732]: from notifications.rb:145:in `initialize'
Jul 25 02:44:38 teknologism com.apple.collabd.notifications[732]: from notifications.rb:439:in `new'
Jul 25 02:44:38 teknologism com.apple.collabd.notifications[732]: from notifications.rb:439
Jul 25 02:44:38 teknologism com.apple.launchd[1] (com.apple.collabd.notifications[732]): Exited with code: 1
Jul 25 02:44:38 teknologism com.apple.launchd[1] (com.apple.collabd.notifications): Throttling respawn: Will start in 9 seconds
Jul 25 02:44:39 teknologism mdworker[734]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 135883 swapped: 2 regions: 414), hit usage threshold importing /private/var/db/swupd/html/content/downloads/15/21/061-7052/gSgFsrpjkJ5vvNrbcsd MwphFYDcTpKWTmC/Savin_PrinterSupport.smd.previous, exiting to clean up.
Jul 25 02:44:44 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 5 seconds
Jul 25 02:44:48 teknologism com.apple.collabd.notifications[738]: /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put': Couldn't connect to server (Curl::Err::ConnectionFailedError)
Jul 25 02:44:48 teknologism com.apple.collabd.notifications[738]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put'
Jul 25 02:44:48 teknologism com.apple.collabd.notifications[738]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:102:in `sendRequest'
Jul 25 02:44:48 teknologism com.apple.collabd.notifications[738]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:153:in `execute'
Jul 25 02:44:48 teknologism com.apple.collabd.notifications[738]: from notifications.rb:145:in `initialize'
Jul 25 02:44:48 teknologism com.apple.collabd.notifications[738]: from notifications.rb:439:in `new'
Jul 25 02:44:48 teknologism com.apple.collabd.notifications[738]: from notifications.rb:439
Jul 25 02:44:48 teknologism com.apple.launchd[1] (com.apple.collabd.notifications[738]): Exited with code: 1
Jul 25 02:44:48 teknologism com.apple.launchd[1] (com.apple.collabd.notifications): Throttling respawn: Will start in 9 seconds
Jul 25 02:44:49 teknologism mdworker[740]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 136255 swapped: 2 regions: 413), hit usage threshold importing /private/var/db/swupd/html/content/downloads/22/25/061-6334/r6zDxQxCRGzSsfDfdLN X4hJcGmS7ckVTrT/Aperture2.1.4Update.smd, exiting to clean up.
Jul 25 02:44:54 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 5 seconds
Jul 25 02:44:59 teknologism com.apple.collabd.notifications[746]: /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put': Couldn't connect to server (Curl::Err::ConnectionFailedError)
Jul 25 02:44:59 teknologism com.apple.collabd.notifications[746]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put'
Jul 25 02:44:59 teknologism com.apple.collabd.notifications[746]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:102:in `sendRequest'
Jul 25 02:44:59 teknologism com.apple.collabd.notifications[746]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:153:in `execute'
Jul 25 02:44:59 teknologism com.apple.collabd.notifications[746]: from notifications.rb:145:in `initialize'
Jul 25 02:44:59 teknologism com.apple.collabd.notifications[746]: from notifications.rb:439:in `new'
Jul 25 02:44:59 teknologism com.apple.collabd.notifications[746]: from notifications.rb:439
Jul 25 02:44:59 teknologism com.apple.launchd[1] (com.apple.collabd.notifications[746]): Exited with code: 1
Jul 25 02:44:59 teknologism com.apple.launchd[1] (com.apple.collabd.notifications): Throttling respawn: Will start in 9 seconds
Jul 25 02:44:59 teknologism mdworker[749]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 135390 swapped: 2 regions: 413), hit usage threshold importing /private/var/db/swupd/html/content/downloads/09/53/061-4083/DvcrdMLDXTGwQck8TgQ gxWWqGDZJyCvC6X/iMacSoftwareUpdate1.2.1.smd, exiting to clean up.
Jul 25 02:45:04 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 5 seconds
Jul 25 02:45:06 teknologism xscertd-helper[323]: idle timer triggered, exiting
Jul 25 02:45:09 teknologism com.apple.collabd.notifications[757]: /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put': Couldn't connect to server (Curl::Err::ConnectionFailedError)
Jul 25 02:45:09 teknologism com.apple.collabd.notifications[757]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put'
Jul 25 02:45:09 teknologism com.apple.collabd.notifications[757]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:102:in `sendRequest'
Jul 25 02:45:09 teknologism com.apple.collabd.notifications[757]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:153:in `execute'
Jul 25 02:45:09 teknologism com.apple.collabd.notifications[757]: from notifications.rb:145:in `initialize'
Jul 25 02:45:09 teknologism com.apple.collabd.notifications[757]: from notifications.rb:439:in `new'
Jul 25 02:45:09 teknologism com.apple.collabd.notifications[757]: from notifications.rb:439
Jul 25 02:45:09 teknologism com.apple.launchd[1] (com.apple.collabd.notifications[757]): Exited with code: 1
Jul 25 02:45:09 teknologism com.apple.launchd[1] (com.apple.collabd.notifications): Throttling respawn: Will start in 9 seconds
Jul 25 02:45:09 teknologism mdworker[759]: (Normal) Import: Using too many resources after 64 files (wired: 0 resident: 133619 swapped: 2 regions: 413), hit usage threshold importing /private/var/db/swupd/html/content/downloads/51/53/061-5114/Bsmt5MYcHbnbGDpMnGZ vVFhfcs9vX7PhzB/Numbers_103.smd, exiting to clean up.
Jul 25 02:45:14 teknologism com.apple.launchd.peruser.89[244] (com.apple.mdworker.pool.0): Throttling respawn: Will start in 5 seconds
Jul 25 02:45:19 teknologism com.apple.collabd.notifications[773]: /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put': Couldn't connect to server (Curl::Err::ConnectionFailedError)
Jul 25 02:45:19 teknologism com.apple.collabd.notifications[773]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:42:in `http_put'
Jul 25 02:45:19 teknologism com.apple.collabd.notifications[773]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:102:in `sendRequest'
Jul 25 02:45:19 teknologism com.apple.collabd.notifications[773]: from /usr/share/collabd/server/ruby/lib/collaboration/service_client.rb:153:in `execute'
Jul 25 02:45:19 teknologism com.apple.collabd.notifications[773]: from notifications.rb:145:in `initialize'
Jul 25 02:45:19 teknologism com.apple.collabd.notifications[773]: from notifications.rb:439:in `new'
Jul 25 02:45:19 teknologism com.apple.collabd.notifications[773]: from notifications.rb:439
Jul 25 02:45:19 teknologism com.apple.launchd[1] (com.apple.collabd.notifications[773]): Exited with code: 1
Jul 25 02:45:19 teknologism com.apple.launchd[1] (com.apple.collabd.notifications): Throttling respawn: Will start in 9 seconds
The last few lines go in a loop and they also tend to bring the CPU high unti it's fixed.
As soon as I turn off "Dedicate Resources to System Services" and I reboot this problem disappears...
Thanks for any help you may briong.
Anyway, the server runs perfectly well without that option...
Maybe you are looking for
-
CcmSetup is exiting with return code 0 Need Help
Installing SCCM Client on Window 7 Machine, Examining the log file, this caught my eye. <![LOG[Successfully deleted the ccmsetup service]LOG]!><time="13:58:26.463-480" date="05-09-2014" component="ccmsetup" context="" type="1" thread="3656" file="cc
-
Problems Installing Adobe Reader 11
When I try and install Adobe Reader I get an installation error which says the "setup was interrupted before AR 11 could be completely installed. Error code 150210" My OS is Win8 Pro 64bit ( is that the problem) I've closed all running programs and
-
"Database logon failed" error received after upgrading from CR XI to CR 200
We have a bunch of reports that use ttx files and datasets. The code to support this was written and compiled originally using .NET 2.0 and CR XI. After recompiling using .NET 3.5 and CR 2008 (not the version that came with VS2008), when I run the
-
HP office jet 6500 running out of space when printing
I cant get written articles to fit on the printer paper.. It cuts off some words on the end of the paper??
-
IMovie/iPhoto download on new mac
I recently bought brand new iMacs. I can't seem to download the iMovie/iPhoto. I can see that it's listed under Top Free section in the app store, but when I try to get it, it says Buy $14.99. I was under the impression this is free for new machines?