EM gives wrong database status.

Hi!
EM is giving me this status:
The database status is currently unavailable. It is possible that the database is in mount or nomount state. Click 'Startup' to obtain the current status and open the database. If the database cannot be opened, click 'Perform Recovery' to perform an appropriate recovery operation.
While,I can see from SQL plus as a sysdba from v$instance that the database staus is open.
I try to startup the database from EM,but it throws an SQL exception and tells me to shutdown the database.
I say yes.
I get an error: Premature EOF encountered, no trailer found
And the database status is still unavailable.Can anyone help me on this?Thanks.

Check previous posts on the same topic. You never mentioned the O/S either.

Similar Messages

Since iCloud downloaded, mac pro has not been able to sync, unable to save info, bookmarks, lost all contact info, gives wrong info on laptop status

since iCloud downloaded, mac pro has not been able to sync, unable to save info, bookmarks, lost all contact info, gives wrong info on laptop status, help please

since iCloud downloaded, mac pro has not been able to sync, unable to save info, bookmarks, lost all contact info, gives wrong info on laptop status, help please

Dbconsole gives bogus database information

15" PB 1.25 GHz CPU 1G RAM OS 10.3.9
BANNER
Oracle Database 10g Enterprise Edition Release 10.1.0.3.0 - Prod
PL/SQL Release 10.1.0.3.0 - Production
CORE 10.1.0.3.0 Production
TNS for MacOS X Server: Version 10.1.0.3.0 - Production
NLSRTL Version 10.1.0.3.0 - Production
Hi;
I am having trouble with dbconsole. This is new, it has run correctly in the past. I must be guilty of changing something somewhere, but I can't think of what it was.
Sequence of events:
Request a static IP via System Preferences/Network
Entry in /etc/hosts for this IP to resolve to "alg4pb.local"
Set the instance via oemctl
Start the listener
Start the d/b
Register the d/b w/the listener
Start dbconsole via emctl start dbconsole
(This is where I notice the first difference, previously I would connect to dbconsole using port 5500, now it reports 5502.)
Launch Safari
Navigate to the provided address
Here I receive the message:
The database status is currently unavailable. It is possible that the database is in mount or nomount state. Click 'Startup' to obtain the current status and open the database. If the database cannot be opened, click 'Perform Recovery' to perform an appropriate recovery operation.
This is incorrect, I've just started the db.
If I attempt to start it from dbconsole there is an error reported in the dbconsole 'header' part of the page but dbconsole now recognizes that the db is actually open.
SQLException
Io exception: NL Exception was generated
Startup/Shutdown:Confirmation
Current Status     open
Operation     shutdown immediate
Are you sure you want to perform this operation?
So I play along and perform the shutdown here (this succeeds) and then do a startup (which also succeeds). But I am then back to where I started with this message in dbconsole:
Update Message
The database state has been changed successfully from shutdown to open. Note that the current status on this page gets updated when the new status information is uploaded into the repository.
View Details
Database: orcl.alg4pb.local
     The database status is currently unavailable. It is possible that the database is in mount or nomount state. Click 'Startup' to obtain the current status and open the database. If the database cannot be opened, click 'Perform Recovery' to perform an appropriate recovery operation.
Clicking on the Database link simply throws this page back up.
Trying to use the old port number gives this error in Safari:
Safari cant open the page http://alg4pb.local:5500/em because it could not connect to the server alg4pb.local.
Please let me know what I can try to understand what is wrong with this and how I can fix it.
If the answer is "rtfm", I'd love to! But I haven't found the "fm" that I need to "r" about this.
Thanks, Jack

Nope. Refreshing brings back the same incorrect page.
But I have found out something additional in the meantime.
I know why the port number changed. Each time you create a database a different port number is assigned for dbconsole. (Makes sense.)
Looiing in $ORACLE_HOME/install at portlist.ini I see:
Ultra Search HTTP port number =5620
iSQL*Plus HTTP port number =5560
Enterprise Manager Console HTTP Port (ora92) = 5500
Enterprise Manager Agent Port (ora92) = 1830
Enterprise Manager Console HTTP Port (ora101) = 5501
Enterprise Manager Agent Port (ora101) = 1831
Enterprise Manager Console HTTP Port (orcl) = 5502
Enterprise Manager Agent Port (orcl) = 1832
Enterprise Manager Console HTTP Port (orcldemo) = 5500
Enterprise Manager Agent Port (orcldemo) = 1830
I was connecting to my v 9 database with port 5500 and it's connecting to my v 10 database with 5502. What I don't here is that port 5500 has now been assigned to two databases; ora92 (which is the db I created through the v 9 install) and orcldemo which I tried to create by hand in the meantime. This can't be good.
What I wonder now is how I should go about cleaning up portlist.ini or if this file is even "functional" vs. documentary. The attempt to create a second v 9 db failed when I ran catalog.sql and there is no dbca for v 9. Or at least I haven't found it.
So, the little question is what to do with portlist.ini, or what is it's functional equivalent and the big question is how is it possible to create v 9 db's aside from the one created through the initial Oracle install.
Jack

0CRM_OPPT_H (Transaction RSA3 gives wrong result)

Hi gurus,
0CRM_OPPT_H (Transaction RSA3 gives wrong result)
BBPCRM 4.0
BW 3.50 version
I had enhanced the structure "crmt_bw_oppt_h"
and also written a BADI to populate Opportunity header status.
But when I run extract checker RSA3 for CRM data,
I get wrong number of records.
I am having 95 records for Opportunities header data.
Data Records / Call = "100"
Display Extr. Calls = "10"
Above settings, I am retrieving only 61 records.
Data Records / Call = "1"
Display Extr. Calls = "200"
For the above settings in RSA3,
I am able to retrieve 95 records correctly.
The problem is that in RSA1 transaction of BW 3.50 server also,
61 records are being loaded from CRM server.
Could this be a Cache memory problem,
Are any of my BASIS settings a cause for this problem?
Any help is really appreciated and will be rewarded.
Thanks,
Aby Jacob
========

Dear Friends,
I had to do a small correction in my BADI code.
I got a solution from Online SAP HELP portal.
http://help.sap.com/saphelp_nw04/helpdata/en/eb/3e7cf4940e11d295df0000e82de14a/frameset.htm
Notes on BADI Usage
====================
The instance generated through the factory method should be declared
as globally as possible or generally be passed as a parameter
to ensure that the initialization process must be run as rarely as possible
just once would be best. In no case should you discard the instance as soon as
it is generated or repeatedly run the initialization process in a loop.
Within the adapter class interface,
required database accesses are buffered locally,
so that each access is executed once only.
However, repeated initialization makes
the buffer useless and dramatically reduces performance.
Due to the local buffering, you can call Business-Add-In methods
without having to expect considerable performance restrictions,
even if no active implementations exist.
Also, if the definition of the Business-Add-In is filter-dependent,
a single instance is sufficient.
However, you should not do without initialization altogether.
Even if you could call static methods of the implementing
class of the Business-Add-In implementation without an instance,
you would lose the benefit of performance improvement through
the Business-Add-Ins and the possibility of multiple use.
If you switch the method type in the interface from the static method
to the instance method at any time in the future,
many code adjustments are required.
In addition, you can no longer use default code that is provided.
Many Thanks to ROBIN
and the whole SDN team
Aby Jacob ,,,,,

Content Database Status Error in SharePoint 2010 Central Administration

Hi,
I am having a new problem with SharePoint 2010 on Windows Server 2008 R2. I have SQL Server 2008 R2 as SharePoint Database on Windows Server 2008 R2. I have total no. of
Seven Content Databases for one Web Application. I found
two of my Content Databases showing Error under the
Database Status column in Manage Content Database section in
Central Administration. Five Content Databases are showing
Started.
Would someone please guide how to resolve it and whats wrong is going on?
Thanks in advance.

What is the output of:
$db = Get-SPContentDatabase <error'ed db name>
$db.Status
And can you set it to Started?
$db = Get-SPContentDatabase <error'ed db name>
$db.Status = "Online"
$db.Update()
Trevor Seward, MCC
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

How to turn a database status from "in recovery" to "online"?

How to turn a database status from "in recovery" to "online"?
We were trying to turn a datase to offline status using management studio - the operation was closed before it could reach the end.

Hi Brian,
Thanks for your feedback;
I have completed the following actions to solve the issue:
1. Start SQL Server in single user mode.
2. Check database status: there i noticed that it was normal
3. Restart SQL Server in multi-user mode
4. Check database status: normal
5. Check my data: ok
Thank you again
Lulu01
You should have wait for an while or atleaset you need to check in the sql errorlog, what phases it is or if any issues persists that shows in the errorlog messages.
also you would have been used sys.databases, to seewhat's the value for state_desc for your database.
Thanks, Rama Udaya.K (http://rama38udaya.wordpress.com) ---------------------------------------- Please remember to mark the replies as answers if they help and UN-mark them if they provide no help,Vote if they gives you information.

Kodo.util.FatalDataStoreException: Wrong database file version

Hi,
I am using Kodo JDO 3.0.2 together with HSQLDB (non-cached, same process).
It
runs fine. However, after having used a SQL tool such as Aqua Data Studio
to
inspect the database my Java code complains with the message
"kodo.util.FatalDataStoreException: Wrong database file version". I have
to
rebuild the database and extend my classes again to get rid of this error.
Is there some information in the database script that does not survive the
inspection with the SQL tool? How can I work around this?
Thanks for your help
--Bruno

Marc,
It was indeed a version mismatch with my hsqldb libs. My SQL Tool used
version 1.7.2 whereas Kdo used 1.7.0. A quick update of the property file
of
Aqua Data Studio fixed the problem. Thanks for the hint.
--Bruno
Marc Prud'hommeaux wrote:
Bruno-
Without being at all familiar with "Aqua Data Studio", I'll make a
completely shot in the dark guess about what might be happening: you are
using version x of Hypersonic to access the database, and then "Aqua
Data Studio" is using version x+1. When the database is opened with HSQL
version x+1, some internal version identifier in the database file is
incremented, which disallows the previous version of HSQL (which is
being used by Kodo) from opening the file.
Again, this is a blind guess, but if it is the case, then the solution
would be to ensure that you are using the same version of HSQL in both
Kodo and "Aqua Data Studio".
Otherwise, can you post the stack trace of the exception? That might
give some more insight as to why this might be happening.
As an aside, note that Kodo doesn't store or verify any internal
"version" or anything like that, so I very much doubt that it is a
problem with Kodo itself.
In article <c1fihi$igu$[email protected]>, Bruno Schaeffer wrote:
Hi,
I am using Kodo JDO 3.0.2 together with HSQLDB (non-cached, same
process).
It
runs fine. However, after having used a SQL tool such as Aqua Data Studio
to
inspect the database my Java code complains with the message
"kodo.util.FatalDataStoreException: Wrong database file version". I have
to
rebuild the database and extend my classes again to get rid of thiserror.
Is there some information in the database script that does not survivethe
inspection with the SQL tool? How can I work around this?
Thanks for your help
--Bruno
Marc Prud'hommeaux [email protected]
SolarMetric Inc. http://www.solarmetric.com

The database status is currently unavailable.

Hi,
I have a probem in my production database -
Server - Windows 2003
DB - Oracle 10g
When i try to open Enterprise Manager I get the below error message. This was working fine since last month. But I haven't made any changes to this DB. But I noticed that disk space was very less so I deleted files from recycle bin, temp internet files, cookies and some unwanted documents i copied on the server. No disc space is OK. I have 10 GB free space. Also i am getting DB warning notification because table space is 92 % full so I want to increase it. But I dont know why I am getting this because I had already set to grow table space automatically.
Is there any other way to increase table space other than that in Enter prise manager ?
Message:*
*"The database status is currently unavailable. It is possible that the database is in mount or nomount state...."*
I tried to troubleshoot as per some forums but it doesnt work. If i use command prompt or sql plus to connect to DB it works but only enterprise manager has this issue. Also my Documentum Application connected to this DB works fine.
listner is fine. Also I added server login account in 'log on as batch john' in local policies.
I do not have a back up to restore also.
Regards,
Ranjith John

Øyvind Isene wrote:
Regarding the tablespace you may consider extend it yourself and not wait for the autoextend to kick in. This way you avoid future problems if for some strange reason the datafile cannot be extended. Not ignoring this error and being reminded every time the tablespace reaches some limit gives you a feeling of how fast your data grows, which is useful (if the alert comes too often you have to increase with bigger chunks). Autoextend is a feature invented for the lazy dbas out there (imho), a responsible one should not rely on it for production systems with any serious load.
As for the connection problem from EM, I suspect the agent has a connection problem. Have you verified the username and password it is using? Can you connect to the db with the same combination?Yes, I can connect to DB with the same user name and password using command prompt or sql plus. Also my Documentum Application is connecting fine to this oracle DB.
This is the full message.
*"The database status is currently unavailable. It is possible that the database is in mount or nomount state. Click 'Startup' to obtain the current status and open the database. If the database cannot be opened, click 'Perform Recovery' to perform an appropriate recovery operation.":*
Previously I used to get login page but now instead of login page I get this warning. There is also 'Startup' and 'Perform Recovery' button. Even if I use 'startup' button it does not resolve issue. It gives me the bellow message -
SQLException
ORA-28000: the account is locked
Startup/Shutdown:Confirmation
Current Status open
Operation shutdown immediate
Are you sure you want to perform this operation?
I used this to unlock my oracle user yesterday
SQL> alter user username identified by password account unlock;
Regards,
Ranjith john

Select for update gives wrong results. Is it a bug?

Hi,
Select for update gives wrong results. Is it a bug?
CREATE TABLE TaxIds
TaxId NUMBER(6) NOT NULL,
LocationId NUMBER(3) NOT NULL,
Status NUMBER(1)
PARTITION BY LIST (LocationId)
PARTITION P111 VALUES (111),
PARTITION P222 VALUES (222),
PARTITION P333 VALUES (333)
ALTER TABLE TaxIds ADD ( CONSTRAINT PK_TaxIds PRIMARY KEY (TaxId));
CREATE INDEX NI_TaxIdsStatus ON TaxIds ( NVL(Status,0) ) LOCAL;
Insert into TAXIDS (TAXID, LOCATIONID, STATUS) Values (100101, 111, NULL);
Insert into TAXIDS (TAXID, LOCATIONID, STATUS) Values (100102, 111, NULL);
Insert into TAXIDS (TAXID, LOCATIONID, STATUS) Values (100103, 111, NULL);
Insert into TAXIDS (TAXID, LOCATIONID, STATUS) Values (100104, 111, NULL);
Insert into TAXIDS (TAXID, LOCATIONID, STATUS) Values (200101, 222, NULL);
Insert into TAXIDS (TAXID, LOCATIONID, STATUS) Values (200102, 222, NULL);
Insert into TAXIDS (TAXID, LOCATIONID, STATUS) Values (200103, 222, NULL);
--Session_1 return TAXID=100101
select TAXID from TAXIDS where LOCATIONID=111 and NVL(STATUS,0)=0 AND rownum=1 for update
--Session_2 waits commit
select TAXID from TAXIDS where LOCATIONID=111 and NVL(STATUS,0)=0 AND rownum=1 for update
--Session_1
update TAXIDS set STATUS=1 Where TaxId=100101;
commit;
--Session_2 return 100101 opps!?
--Session_1 return TAXID=100102
select TAXID, STATUS from TAXIDS where LOCATIONID=111 and NVL(STATUS,0)=0 AND rownum=1 for update
--Session_2 waits commit
select TAXID, STATUS from TAXIDS where LOCATIONID=111 and NVL(STATUS,0)=0 AND rownum=1 for update
--Session_1
update TAXIDS set STATUS=1 Where TaxId=100102;
commit;
--Session_2 return 100103

This is a bug. Got to be a bug.
This should be nothing to do with indeterminate results from ROWNUM, and nothing to do with read consistency at the point of statement start time in session2., surely.
Session 2 should never return 100101 once the lock from session 1 is released.
The SELECT FOR UPDATE should restart and 100101 should not be selected as it does not meet the criteria of the select.
A statement restart should ensure this.
A number of demos highlight this.
Firstly, recall the original observation in the original test case.
Setup
SQL> DROP TABLE taxids;
Table dropped.
SQL>
SQL> CREATE TABLE TaxIds
2 (TaxId NUMBER(6) NOT NULL,
3   LocationId NUMBER(3) NOT NULL,
4   Status NUMBER(1))
5 PARTITION BY LIST (LocationId)
6 (PARTITION P111 VALUES (111),
7   PARTITION P222 VALUES (222),
8   PARTITION P333 VALUES (333));
Table created.
SQL>
SQL> ALTER TABLE TaxIds ADD ( CONSTRAINT PK_TaxIds PRIMARY KEY (TaxId));
Table altered.
SQL>
SQL> CREATE INDEX NI_TaxIdsStatus ON TaxIds ( NVL(Status,0) ) LOCAL;
Index created.
SQL>
SQL>
SQL> Insert into TAXIDS (TAXID, LOCATIONID, STATUS) Values (100101, 111, NULL);
1 row created.
SQL> Insert into TAXIDS (TAXID, LOCATIONID, STATUS) Values (100102, 111, NULL);
1 row created.
SQL> Insert into TAXIDS (TAXID, LOCATIONID, STATUS) Values (100103, 111, NULL);
1 row created.
SQL> Insert into TAXIDS (TAXID, LOCATIONID, STATUS) Values (100104, 111, NULL);
1 row created.
SQL> Insert into TAXIDS (TAXID, LOCATIONID, STATUS) Values (200101, 222, NULL);
1 row created.
SQL> Insert into TAXIDS (TAXID, LOCATIONID, STATUS) Values (200102, 222, NULL);
1 row created.
SQL> commit;
Commit complete.
SQL> Original observation:
Session1>SELECT taxid
2 FROM   taxids
3 WHERE locationid    = 111
4 AND    NVL(STATUS,0) = 0
5 AND    ROWNUM        = 1
6 FOR UPDATE;
     TAXID
    100101
Session1>
--> Session 2 with same statement hangs until
Session1>BEGIN
2   UPDATE taxids SET status=1 WHERE taxid=100101;
3   COMMIT;
4 END;
5 /
PL/SQL procedure successfully completed.
Session1>
--> At which point, Session 2 returns
Session2>SELECT taxid
2 FROM   taxids
3 WHERE locationid    = 111
4 AND    NVL(STATUS,0) = 0
5 AND    ROWNUM        = 1
6 FOR UPDATE;
     TAXID
    100101
Session2>There's no way that session 2 should have returned 100101. That is the point of FOR UPDATE. It completely reintroduces the lost UPDATE scenario.
Secondly, what happens if we drop the index.
Let's reset the data and drop the index:
Session1>UPDATE taxids SET status=0 where taxid=100101;
1 row updated.
Session1>commit;
Commit complete.
Session1>drop index NI_TaxIdsStatus;
Index dropped.
Session1>Then try again:
Session1>SELECT taxid
2 FROM   taxids
3 WHERE locationid    = 111
4 AND    NVL(STATUS,0) = 0
5 AND    ROWNUM        = 1
6 FOR UPDATE;
     TAXID
    100101
Session1>
--> Session 2 hangs again until
Session1>BEGIN
2   UPDATE taxids SET status=1 WHERE taxid=100101;
3   COMMIT;
4 END;
5 /
PL/SQL procedure successfully completed.
Session1>
--> At which point in session 2:
Session2>SELECT taxid
2 FROM   taxids
3 WHERE locationid    = 111
4 AND    NVL(STATUS,0) = 0
5 AND    ROWNUM        = 1
6 FOR UPDATE;
     TAXID
    100102
Session2>Proves nothing, Non-deterministic ROWNUM you say.
Then let's reset, recreate the index and explicity ask then for row 100101.
It should give the same result as the ROWNUM query without any doubts over the ROWNUM, etc.
If the original behaviour was correct, session 2 should also be able to get 100101:
Session1>SELECT taxid
2 FROM   taxids
3 WHERE locationid    = 111
4 AND    NVL(STATUS,0) = 0
5 AND    taxid         = 100101
6 FOR UPDATE;
     TAXID
    100101
Session1>
--> same statement hangs in session 2 until
Session1>BEGIN
2   UPDATE taxids SET status=1 WHERE taxid=100101;
3   COMMIT;
4 END;
5 /
PL/SQL procedure successfully completed.
Session1>
--> so session 2 stops being blocked and:
Session2>SELECT taxid
2 FROM   taxids
3 WHERE locationid    = 111
4 AND    NVL(STATUS,0) = 0
5 AND    taxid         = 100101
6 FOR UPDATE;
no rows selected
Session2>Of course, this is how it should happen, surely?
Just to double check, let's reintroduce ROWNUM but force the order by to show it's not about read consistency at the start of the statement - restart should prevent it.
(reset, then)
Session1> select t.taxid
2   from
3    (select taxid, rowid rd
4      from   taxids
5      where locationid = 111
6      and    nvl(status,0) = 0
7      order by taxid) x
8   , taxids t
9   where t.rowid = x.rd
10   and   rownum = 1
11   for update of t.status;
     TAXID
    100101
Session1>
--> Yes, session 2 hangs until...
Session1>BEGIN
2   UPDATE taxids SET status=1 WHERE taxid=100101;
3   COMMIT;
4 END;
5 /
PL/SQL procedure successfully completed.
Session1>
--> and then
Session2> select t.taxid
2   from
3    (select taxid, rowid rd
4      from   taxids
5      where locationid = 111
6      and    nvl(status,0) = 0
7      order by taxid) x
8   , taxids t
9   where t.rowid = x.rd
10   and   rownum = 1
11   for update of t.status;
     TAXID
    100102
Session2>Session 2 should never be allowed to get 100101 once the lock is released.
This is a bug.
The worrying thing is that I can reproduce in 9.2.0.8 and 11.2.0.2.

Database Status report.

Hi Export,
Currently i joined a company as a Oracle Dba. i am new to DBA world, My manager told me to prepare a database status report. Please suggest me how can i create the report.
Regards...
Asmit

EdStevens wrote:
marksmithusa wrote:
That's an awesome idea - just one problem.
If it's tall enough for all to see, this also includes management and if they notice the chicken, your cube will be instantly surrounded by various management types asking 'when will it be back up?'
You're, almost literally, hoisting yourself with your own petard.True, but I think he had the understanding with mgmt that if the chicken was up, they'd best leave him alone until the chicken came down.Wow. I'm actually stunned - I didn't think that was possible within the physical laws of the universe that we occupy.
He achieved 'DBA Hero' status.

How to give out a status message indicating the number of fields selected

Hi experts,
I hope some one might have done what I'm trying to do. Could some one please show me how to give out a status message saying for example how many fields have been give out(or selected) in the t_ouput in an alv grid? Is there a FM that could do this? I mean like giving the FM the t_output and it will show a status message with the number of fields selected?
Thank you for your input.
Nadin
Message was edited by:
nadin ram

Hi Ram,
Write this code,
Message 'Select Only Ten Fields' type 'I'.
It displays The Message in Message Box.
Or if you want the Error Message means,
Message 'Select Only Ten Fields' type 'E'.
Thanks,
reward If Helpful.

Wireless keyboard gives wrong letters

wireless keyboard gives wrong letters

[shameful mode on]
Sorry. I don't have my Mac in front of me.
I'm using windows right now.
[shameful mode off]

CALCULATE_TAX_ITEM gives wrong values for Scess and HScess in PO Print

Dear Friends,
I am working with PO Print in smartforms hare the Fm CALCULATE_TAX_ITEM is gives wrong values for Scess and HEcess if I put the Gate pass (Basic Excise Duty) Manually.
And one more Issue is as if I check any line item condition taxes than imediatly when I see the print the all line items Scee and HEcess displays same which I have saw.
If there is a single line item in PO than there is no issue any way.
kindly suggest to resolve the issue.
Regards,
D Tarun Kumar

Hi,
I had the same issue, that taxes on invoice tab of PO was not printed correctly on PO form by calling CALCULATE_TAX_ITEM.
If you want to have the same tax value as komp-mwsbp, that use following form routine call before FB CALCULATE_TAX_ITEM.
perform j_1b_save_tax_fields(saplmepo) using ekko ekpo lfa1.
This is used in transaction me23n also.
Kind regards,
Tülay

Current database status does not match sitemap page

After I had to drop and recreate an 10g instance the OEM Home tab displays Status Pending. The instance, however, is available and all other OEM functions like Performance, Installation, and Maintenance work fine.
If I try to shutdown the instance the I get this message in the Startup/Shutdown:Confirmation screen :
Current Status open
This is the correct current database status, although it doesn't match the current status in the sitemap page.
Stopping and starting the instance through OEM did not change this condition.
How do you get OEM to update the status to what it knows it correct instead of what is stored in the sitemap page?

Ok, I did that many times already. The command is 'emctl stop dbconsole' and 'enctl start dbconcole'. OEM still thinks the instance is Pending.
Becasue of this and other problems with this instance I am going to cut my losses and uninstall 10.1 then reinstall 10.2 this weekend.
For example, I am now getting messages like this on Startup and the database will not Open:
ORA-04030: out of process memory when trying to allocate 41987820 bytes (pga
heap,KCL disk IO request block array)
If I allocate much LESS memory to SGA and PGA and then Startup the instance comes right up.
Thanks for you help.

My Sites database status changed to "Database is up to date, but some sites are not completely upgraded."

We have a brand new SharePoint 2013 farm which we just put into production. As users have begun creating their My Sites, the My Sites web application database changed to a status of "Database is up to date, but some sites are not completely upgraded."
Huh?
Prior to deploying to production, we had some test users that had created My Sites, and everything was fine. The database status was "No action required".
Anyone know why the creation of My Sites would cause the database status to flip to this warning?

HI Kleung,This seems to be that after the patch upgradation some of the sites are not upgraded properly.Please check the below thread that exactly talking about the issue that see in your enviornment.
http://expertsharepoint.blogspot.de/2014/03/data-base-is-up-to-date-but-some-sites.html
First of all, to identify what site collection doesn't got upgraded.
 Run: stsadm.exe -o localupgradestatus > upgradestatus.txt
or
PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures (Run from one of the WFE server)
In below as you see, there no site collection that need upgrade. If you have any, you can identify
them by searching by word "Needs upgrade" in this file.
Secondly, run the command in the Power Shell:
For resuming the upgrade, you’ll need the ID for the database :
Get-SPContentDatabase -Identity <your content database name>
When you got the GUID for the database you can then resume the upgrade
 upgrade-spcontentdatabase -id <database
GUID>
Finally, check the upgrade status by running stsadm again:
stsadm.exe -o localupgradestatus > upgradestatus.
Thanks
Anil Avula See Me At: http://expertsharepoint.blogspot.de/

EM gives wrong database status.

Similar Messages

Maybe you are looking for