Globe Logo During Macbook Startup
I have a macbook, and owned it for almost a year now.
Ever since i updated that firmware, I have some issues with startup.
When I start-up I always get a globe logo sign that used to come out only when I had some sort of updates.
Also, I realized that when i am hooked into a network via ethernet cable the globe logo pops out for almost about a min or longer.
either case, I don't like it slowing down my startup time.
Please let me know if there are any solutions
The post above mine answers the question, I just wanted to offer a quick explanation. Somehow, your startup disk is set to Network, which is checking your network for a networked harddrive to boot from. I assume what's happening is that it's not finding one, it boots from the secondary source, OS X.
Similar Messages
-
A streak across apple logo during startup??
I don't know anyone posted this before, but i look through a few page cant find any solution.
i just got my iphone 3G yesterday. I discovered the Apple logo had a so-called a cut/ line/ streak across on the apple logo during the iPhone startup.
is that the normal apple logo on iphone3G or there is something wrong with mine.?
thx
Message was edited by: echeanThere's already a post on this. You should do a search on this next time.
Anyway, look at the top nav of this page and then look at the first tab where there is an Apple logo. It has the same streak. Is there something wrong with this website?
No, it's part of the Apple logo so you're okay. -
Gray bar under Apple logo during startup with 10.7.2
Hi everyone,
first-time iMac owner since May 2011, I'm experiencing exactky the same problem described in the article Mac OS X v10.6: Gray progress bar appears under Apple logo during startup, but with two important differences:
it never happened with the original the 10.6 factory-installed, and started to appear after upgrading to 10.7 at the beginning of August
my iMac, included in the HD replacement program announed by Apple in July 2011, had the HD replaced with a new one in October 2011
In addition to the behavious described in the KB article, it's worth noting that, when one finally manages to log in (and the gray bar may take one good minute to disappear, which happens after filling up to approx. 60-70% of its length), the iMac is barely unusable, as the graphic interface is suddenly **** slow and there's a lot of flickering.
Since seeing is believing, please have allok at the YouTube video I made on this "false start", as I named it: see iMac_falsa_partenza / iMac_false_start.
I had already reported the problem to the local assistance, and they had told me it was an evidence of the HD problem indicated by Apple. Then they replaced the HD (...did they, actually? Probably yes, as the HD now installed is far noisier than the old one), but the very same day I brought it back from the assistance, at the second start... bam, here's the nasty gray bar again.
I didn't further report the problem to the assistance because my faith in their capability has cracked and because the simple replacement of the HD took them three full weeks. But this "false start" issue really, really bothers me a lot, as it happens every other day.
How can I have some good Apple expert technicians take this problem seriously and help me solving it?
As a first-time owner of a Mac, I have onestly to say I'm much, much disappointed by this story... Thanks anyone for any help.If you can't eject a CD or DVD or open the drive tray
How do I eject a defective DVD?: Apple Support Communities
http://www.faqforge.com/macosx/how-to-eject-a-cd-in-a-mac-mini-with-pc-keyboard- and-mouse/ -
Why does a flashing world globe appear during start-up process?
In recent months my MacBook Pro has decided not to start up in the usual way. Now, when I am starting up a blank white screen appears for 55 sec, then a flashing world globe appears for 65 sec before the Apple logo appears. The machine is ready to go after a further 75 sec. Does any one know why this flashing world globe has suddenly come into my life - never seen it before?
System Preferences>Startup Disk - Select your OS hard drive and lock the padlock. Restart your computer. Still seeing the flashing world globe?
BTW: The flashing world globe is a network startup disk. -
Sometimes when booting up my Macbook, the Mail app comes up during login/startup. I do not have an account configured, so the "Welcome to Mail" screen comes up, asking me to create an account.
This does not happen all the time. Randomly.
I do not have Mail in my login items.
Any ideas why this happens and how i can make it stop?HI and Welcome to Apple Discussions...
Well, if you don't have it set up in System Preferences/Accounts - Login Items then go to /Library/Startup Items and see if it's listed there.
If you have a Dashboard widget that is related in anyway to how your Mac Mail application runs, that could be the culprit also.
Carolyn -
Macbook Startup CD-ROM Sound normal ?
Hello,
I'm new to mac and I wonder if it's normal on Macbook startup that the combodrive tries to eject or to pull in a cd ? Typically there is no cd inserted at boot up. The combodrive makes sound before the mac startup sound appears. The same effect after waking up from sleep mode.
Is this normal?
Best Regards,
MaikWelcome to the Forum.
Yes. It's absolutely normal.
As you get to know your computer, you may hear small noises during startup and when using your hard disk and optical drive. For example, your hard disk and optical drive may whir and click as they access information or load and eject discs. After the computer runs for some time, a fan or fans may turn on to cool it, producing a faint sound. Small noises are part of the computer’s normal functioning. -
After Effects can't continue: unexpected failure during application startup
Im running 10.10, Mac OSX, it was running fine before a minor update came out, and now I can not open AE CS6. I have uninstalled, reinstalled it, installed the trial of CC 2014. No messages beside "After Effects can’t continue: unexpected failure during application startup" come up.
System log:
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.0 instead of 10.10.0. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.
Call location:
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 0 CarbonCore 0x00007fff82bb637d ___Gestalt_SystemVersion_block_invoke + 113
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 1 libdispatch.dylib 0x00007fff8bf70fa2 _dispatch_client_callout + 8
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 2 libdispatch.dylib 0x00007fff8bf70f00 dispatch_once_f + 79
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 3 CarbonCore 0x00007fff82b5e932 _Gestalt_SystemVersion + 987
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 4 CarbonCore 0x00007fff82b5e51f Gestalt + 144
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 5 AdobeCrashDaemon 0x0000000100002e69 -[MyDaemon GetOSVersionMajor] + 33
Jun 22 15:30:49 Users-iMac.local AdobeCrashDaemon[976]: 6 AdobeCrashDaemon 0x0000000100002d4a -[MyDaemon isRunningOnLeopard] + 25Well, looks like a bug in Yosemite. You might wanan read the pertinent announcements, anyway. At this point Adobe apps are not compatible with OSX 10.10.
Mylenium -
How can I disable the behance pics during the startup of my CC 2014 programmes?
When I start my photoshop cc 2014 and illustrator and all other apps, there ware always some behance pics from users.
is there a way to disable them?
thanks a lot
alexhi sarah,
thanks for getting back to me.
i mean these images:
when the programmes are starting up…
thanks a lot for your help
alex
Am 08.01.2015 um 16:05 schrieb SarahBehance1 <[email protected]>:
How can I disable the behance pics during the startup of my CC 2014 programmes?
created by SarahBehance1 in Behance - View the full discussion
HI Alex - can you send a screenshot of what you're seeing? I'm not sure what you're referring to.
Talk to you soon, thanks!
If the reply above answers your question, please take a moment to mark this answer as correct by visiting: https://forums.adobe.com/message/7077548#7077548 and clicking ‘Correct’ below the answer
Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page:
Please note that the Adobe Forums do not accept email attachments. If you want to embed an image in your message please visit the thread in the forum and click the camera icon: https://forums.adobe.com/message/7077548#7077548
To unsubscribe from this thread, please visit the message page at , click "Following" at the top right, & "Stop Following"
Start a new discussion in Behance by email or at Adobe Community
For more information about maintaining your forum email notifications please go to https://forums.adobe.com/thread/1516624.
Alex an der Haas
Art Direction
// Die Goldkinder
// Ausdenken und Machen.
// Mollardgasse 85A / Stiege 3 / Top 142, 1060 Wien
// Tel: +43 (0) 1 595.37.07
// Mob: +43 (0) 699.816.366.31
// http://www.diegoldkinder.at -
After upgrading HANA from rev. 69.1 to rev.72 OOM errors occure during HDB startup
Hello,
we upgraded our HANA scale out system from rev. 69.1 to rev. 72.
~4 hours after the upgrade our HDB crashed with OOM errors on the master indexserver.
Since than we are trying to start it back up and face OOM errors during startup in the index rebuild phase:
The errors clearly state the HANA runs out of allocatable memory for Pool/IndexRebuildAllocator during startup.
It looks like HANA requires more memory during this phase compared to rev. 69.1
Our Master node has 512GB of physical memory and the Allocation limit is set to 95% of this (default).
Here is what we read from our logs during startup:
[3331]{-1}[-1/-1] 2014-03-24 01:35:36.735498 i Service_Startup ptime_master_start.cc(00719) : Rebuilding system indexes.
[3331]{-1}[-1/-1] 2014-03-24 01:35:37.236971 i Service_Startup ptime_master_start.cc(00733) : Rebuilding system indexes done.
[3331]{-1}[-1/-1] 2014-03-24 01:35:37.237002 i Service_Startup ptime_master_start.cc(00735) : Rebuilding indexes.
[3331]{-1}[-1/-1] 2014-03-24 01:35:37.244660 i Service_Startup IndexManager_rebuild.cc(00478) : Number of indexes: 2837
[3331]{-1}[-1/-1] 2014-03-24 01:35:37.245606 i Service_Startup IndexManager_rebuild.cc(00580) : Number of JobEx indexes: 2798
[3367]{-1}[9/-1] 2014-03-24 01:36:33.729391 w ResMan ResourceContainer.cpp(01300) : Information about shrink at 24.03.2014 01:28:46 000 Mon:
Reason for shrink: Precharge for big block allocation. User size: 6269307200
ShrinkCaller
[4123]{-1}[9/-1] 2014-03-24 01:36:42.465154 w Memory PoolAllocator.cpp(01060) : Out of memory for Pool/IndexRebuildAllocator, size 48B, flags 0x0
[4123]{-1}[9/-1] 2014-03-24 01:36:42.465168 e Memory ReportMemoryProblems.cpp(00733) : OUT OF MEMORY occurred.
[3538]{-1}[9/-1] 2014-03-24 01:36:42.465164 w Memory PoolAllocator.cpp(01060) : Out of memory for Pool/IndexRebuildAllocator, size 48B, flags 0x0
[3538]{-1}[9/-1] 2014-03-24 01:36:42.465177 e Memory ReportMemoryProblems.cpp(00733) : OUT OF MEMORY occurred.
[4123]{-1}[9/-1] 2014-03-24 01:36:42.465168 e Memory ReportMemoryProblems.cpp(00733) : Failed to allocate 48 byte.
[3538]{-1}[9/-1] 2014-03-24 01:36:42.465177 e Memory ReportMemoryProblems.cpp(00733) : Failed to allocate 48 byte.
[4123]{-1}[9/-1] 2014-03-24 01:36:42.465168 e Memory ReportMemoryProblems.cpp(00733) : Current callstack:
[3538]{-1}[9/-1] 2014-03-24 01:36:42.465177 e Memory ReportMemoryProblems.cpp(00733) : Current callstack:
[3562]{-1}[9/-1] 2014-03-24 01:36:42.465245 w Memory PoolAllocator.cpp(01060) : Out of memory for Pool/IndexRebuildAllocator, size 48B, flags 0x0
[3562]{-1}[9/-1] 2014-03-24 01:36:42.465256 e Memory ReportMemoryProblems.cpp(00733) : OUT OF MEMORY occurred.
GLOBAL_ALLOCATION_LIMIT (GAL) = 520645177866b (484.88gb), SHARED_MEMORY = 243742983024b (227gb), CODE_SIZE = 6919073792b (6.44gb)
PID=2987 (hdbnameserver), PAL=487793667686, AB=1596952576, UA=0, U=1415644701, FSL=0
PID=3196 (hdbcompileserve), PAL=487793667686, AB=447041536, UA=0, U=356200477, FSL=0
PID=3193 (hdbpreprocessor), PAL=487793667686, AB=416477184, UA=0, U=292814063, FSL=0
PID=3254 (hdbstatisticsse), PAL=54199296409, AB=1040187392, UA=0, U=862081043, FSL=0
PID=3257 (hdbxsengine), PAL=487793667686, AB=1100451840, UA=0, U=907234077, FSL=0
PID=3251 (hdbindexserver), PAL=487793667686, AB=265382010522, UA=0, U=218447843045, FSL=0
Total allocated memory= 520645177866b (484.88gb)
Total used memory = 472943874222b (440.46gb)
Sum AB = 269983121050
Sum Used = 222281817406
Heap memory fragmentation: 9
Top allocators (ordered descending by inclusive_size_in_use).
1: / 218448756093b (203.44gb)
2: Pool 214254480696b (199.53gb)
3: Pool/IndexRebuildAllocator 196297409104b (182.81gb)
4: Pool/PersistenceManager 9920106968b (9.23gb)
5: Pool/PersistenceManager/PersistentSpace(0) 9779577952b (9.10gb)
6: Pool/PersistenceManager/PersistentSpace(0)/RowStoreLPA 9473884512b (8.82gb)
7: Pool/ResourceContainer 2852314824b (2.65gb)
8: AllocateOnlyAllocator-unlimited 2832931544b (2.63gb)
9: Pool/malloc 2660566632b (2.47gb)
10: Pool/malloc/libhdbrskernel.so 2467813288b (2.29gb)
11: Pool/RowEngine 2284285840b (2.12gb)
12: AllocateOnlyAllocator-unlimited/FLA-UL<3145728,1>/MemoryMapLevel2Blocks 2135949312b (1.98gb)
13: AllocateOnlyAllocator-unlimited/FLA-UL<3145728,1> 2135949312b (1.98gb)
14: Pool/RowEngine/CpbTree 1417842512b (1.32gb)
15: AllocateOnlyAllocator-limited 1184520640b (1.10gb)
16: AllocateOnlyAllocator-limited/ResourceHeader 1184517680b (1.10gb)
17: Pool/RowEngine/LockTable 536881408b (512mb)
18: AllocateOnlyAllocator-unlimited/FLA-UL<120,256>/BigBlockInfoAllocator 360752520b (344.04mb)
19: AllocateOnlyAllocator-unlimited/FLA-UL<120,256> 360752520b (344.04mb)
20: Pool/PersistenceManager/PersistentSpace(0)/RowStoreConverter 239921680b (228.80mb)
Top allocators (ordered descending by exclusive_size_in_use).
1: Pool/IndexRebuildAllocator 196297409104b (182.81gb)
2: Pool/PersistenceManager/PersistentSpace(0)/RowStoreLPA 9473884512b (8.82gb)
3: Pool/ResourceContainer 2852314824b (2.65gb)
4: Pool/malloc/libhdbrskernel.so 2467813288b (2.29gb)
5: AllocateOnlyAllocator-unlimited/FLA-UL<3145728,1>/MemoryMapLevel2Blocks 2135949312b (1.98gb)
6: Pool/RowEngine/CpbTree 1417842512b (1.32gb)
7: AllocateOnlyAllocator-limited/ResourceHeader 1184517680b (1.10gb)
8: Pool/RowEngine/LockTable 536881408b (512mb)
9: AllocateOnlyAllocator-unlimited/FLA-UL<120,256>/BigBlockInfoAllocator 360752520b (344.04mb)
10: Pool/PersistenceManager/PersistentSpace(0)/RowStoreConverter/ConvPage 239075328b (228mb)
11: Pool/RowEngine/Internal 205837824b (196.30mb)
12: StackAllocator 176672768b (168.48mb)
13: AllocateOnlyAllocator-unlimited/FLA-UL<48,128>/FreeBigBlockInfoAllocator 144301008b (137.61mb)
14: Pool/RowEngine/Transaction 103391528b (98.60mb)
15: Pool/malloc/libhdbexpression.so 90507984b (86.31mb)
16: Pool/malloc/libhdbbasement.so 90380472b (86.19mb)
17: AllocateOnlyAllocator-unlimited/ReserveForUndoAndCleanupExec 84029440b (80.13mb)
18: AllocateOnlyAllocator-unlimited/ReserveForOnlineCleanup 84029440b (80.13mb)
19: Pool/Statistics 83825720b (79.94mb)
20: Pool/PersistenceManager/ContainerNameDirectory 59182968b (56.44mb)
In order to fix this bottleneck, we first need to get HDB started, but how?
Is there a way to aviod that row store tables are being loaded during startup? (this would allow enough memory for the index rebuild)
Is there a way to skip the index rebuild during startup?
Can we increase the allocation limit to more than 95% of the physical memory? (e.g. we could configure swap space to be utilized, just to get over the edge of this during the startup in order to bring our HDB back up and work on reducing the memory requirement on the master index server)
Kind Regards
Florian Wittmann
ps. we also have a call with SAP.To update everyone who runs into the same issue during startup of HANA, here is the solution that has worked for us. But I highly recommend to have such an approach reviewed by SAP service before I you perform this!
For us the only chance left to bring HANA up was to configure swap space on the master node. (We configured 20GB...we could not know how much memory it would need during the startup to get passed the index rebuild, so that was just a guess that turned out to be just enough for us to get passed that memory peak during the startup phase).
After that we adjusted the custom parameter file /sapmnt/<SID>/global/hdb/custom/config/global.ini
and maintained a global_allocation_limit that we manually calculated as (512GB physical mem. + 20GB swap mem.)/0.95
e.g.
[memorymanager]
global_allocation_limit=517530
Than we started HANA up again and made use of the page file during the index rebuild in the startup phase...of course this dramatically slows down the startup...well you do an index reorg using swap space...but after 1hour we got passed the index rebuild and memory utilization went down again. (With this error we learned that HANA has a significantly higher memory consumption during startup and the upgrade from SP 6 to SP 7 must have even increased this slightly, since we managed to startup our HANA db before upgrading without this issue, but it was not the root cause!)
Now that we had HANA back up, we investigated memory consuming indices together with SAP, and with the help of below query, we identified row store table RSMONMESS to hold 25GB of 2ndary indices!
select table_name, round((sum(index_size)) / 1024 / 1024, 2) as
SIZE_IN_MB, count(*) as number_of_indexes from M_RS_INDEXES group by
table_name order by SIZE_IN_MB desc
Before droping 2ndary indices:
TABLE_NAME;SIZE_IN_MB;NUMBER_OF_INDEXES
RSMONMESS;30.883,8;6
drop index SAP<SID>."RSMONMESS~AXX";
drop index SAP<SID>."RSMONMESS~TIM";
drop index SAP<SID>."RSMONMESS~AU1";
drop index SAP<SID>."RSMONMESS~RID";
drop index SAP<SID>."RSMONMESS~AXY";
After drop:
TABLE_NAME;SIZE_IN_MB;NUMBER_OF_INDEXES
RSMONMESS;5.708,43;1
With that change we reset our custom parameter on global_allocation_limit and went back to the default (95% of main physical mem.), removed the swap file and started up HANA again...and during this startup we managed to stay in our global_allocation_limit and bring HANA back up again! -
There is always a blue screen appears after the Apple logo during the booting process. And then everything is back to normal. What is this thing? Is there something wrong with my screen or something?
Nah - that's just the normal boot process.
Clinton -
10.1.3.5 - unable to find ws-addressing.xsd during SOA startup
I see the following messages in my logs during server startup any clue how to fix this ? the file seems to be there under bpel/system/xmllib
<2010-01-07 17:02:13,718> <DEBUG> <collaxa> <ProcessJob::execute> Attempt (2/30) ... testing http access to server
<2010-01-07 17:02:13,718> <DEBUG> <collaxa> <ProcessJob::execute> Trying http connection to http://myhost:80/orabpel/xmllib/ws-addressing.xsd
<2010-01-07 17:02:13,718> <DEBUG> <collaxa> <ProcessJob::execute> Trying to get /orabpel/xmllib/ws-addressing.xsd
<2010-01-07 17:02:13,718> <DEBUG> <collaxa> <ProcessJob::execute> URL http://myhost:80/orabpel/xmllib/ws-addressing.xsd returned status 404
<2010-01-07 17:02:13,718> <DEBUG> <collaxa> <ProcessJob::execute> Trying http connection to http://myhost:80/orabpel/xmllib/ws-addressing.xsd
<2010-01-07 17:02:13,718> <DEBUG> <collaxa> <ProcessJob::execute> Trying to get /orabpel/xmllib/ws-addressing.xsd
<2010-01-07 17:02:13,734> <DEBUG> <collaxa> <ProcessJob::execute> URL http://myhost:80/orabpel/xmllib/ws-addressing.xsd returned status 404
<2010-01-07 17:02:13,734> <DEBUG> <collaxa> <ProcessJob::execute> Trying http connection to http://10.10.10.10:80/orabpel/xmllib/ws-addressing.xsd
<2010-01-07 17:02:13,734> <DEBUG> <collaxa> <ProcessJob::execute> Trying to get /orabpel/xmllib/ws-addressing.xsd
<2010-01-07 17:02:13,734> <DEBUG> <collaxa> <ProcessJob::execute> URL http://10.10.10.10:80/orabpel/xmllib/ws-addressing.xsd returned status 404
<2010-01-07 17:02:13,734> <DEBUG> <collaxa> <ProcessJob::execute> Trying http connection to http://myhost:80/orabpel/xmllib/ws-addressing.xsd
<2010-01-07 17:02:13,734> <DEBUG> <collaxa> <ProcessJob::execute> Trying to get /orabpel/xmllib/ws-addressing.xsd
<2010-01-07 17:02:13,734> <DEBUG> <collaxa> <ProcessJob::execute> URL http://myhost:80/orabpel/xmllib/ws-addressing.xsd returned status 404
<2010-01-07 17:02:13,734> <DEBUG> <collaxa> <ProcessJob::execute> Trying http connection to http://localhost:80/orabpel/xmllib/ws-addressing.xsd
<2010-01-07 17:02:13,734> <DEBUG> <collaxa> <ProcessJob::execute> Trying to get /orabpel/xmllib/ws-addressing.xsd
<2010-01-07 17:02:13,734> <DEBUG> <collaxa> <ProcessJob::execute> URL http://localhost:80/orabpel/xmllib/ws-addressing.xsd returned status 404
<2010-01-07 17:02:13,734> <ERROR> <collaxa> <ProcessJob::execute> Attempt (2/30) ... failed to connect ... retrying in 15 seconds ...Hi,
Thanks a lot for your reply.
I set the ORACLE_HOME and WL_HOME to E:\OraHome\10g
But still the same error is coming.
I have already installed Weblogic server 10.3 in E:\OraHome\10g
When I try to install the SOA suite here is the step I am following
1) Source: F:\download\SOA\10g\ias_windows_x86_101351\Disk1\stage\products.xml
Destination: Name: oracleas
Path: E:\OraHome\10g
2) Language Selection
3) Weblogic server location: E:\OraHome\10g\wlserver_10.3
here when I press next it is throwing the error "The ORACLE_HOME needs to be at the same level as WL_HOME"
Do I need any preinstallation like database before going for SOA suite?
Thanks,
Balaram -
Message in alert log file during the startup of the DB
Hi,
i have two instances, i have the same warning in the alert log file during the startup of the DB:
Oracle instance running on a system with low open file descriptor limit.
Tune your system to increase this limit to avoid severe performance degradation.
The db_files parameter was at 1024 for the two instances, i have set it to 300 for the first instance and 550 for second, the message for the first instance was droped(it's ok), but the message was there in the alert log for the second instance.
The two instance are on the same machine.
The number of the open file limit on the linux machine is equal to 1024.
I have shutdown the first instance (with db_files=300) the problem persits for the second instance (with db_files=550).
My question is how to determinate the right value of db_files parameter to avoid this message.
Regards.
Message was edited by:
learnIncrease the max number of open file on Linux or decrease db_files.
f the OS limit is 1024 db_files would have to be >= 472 for the message to be printed. t is printed if an instance is configured to access more datafiles than the OS-specific limit on the number of files that can be open in a single process. In this case the server will re-cycle the file descriptors.
Vadim Bobrov
Oracle Database Tools
http://www.fourthelephant.com -
Diskgroup not mounted during cluster startup
Hi,
I have a 2 node RAC(11GR2) on VMWare 7.1.4. OS is Solaris 10
I have registered 2 instances in the cluster.
srvctl add database -d dbrac -o /u01/app/oracle/product/11.2.0/dbhome_1 -a "extdg,nordg"
srvctl add instance -d dbrac -i dbrac2 -n vmsol2
srvctl add instance -d dbrac -i dbrac1 -n vmsol1
After after registering the 2 instances, initially the instance were automatically up when ever I execute a ./crsctl start cluster.
But now the database instances on both nodes are not comming up; only ASM is up.
While checking ASM disk group, I found EXTDG and NORDG is not mounted. So I mounted the disk group and started the database.
Then I manually mounted, the disk groups and started the database.
SQL> alter diskgroup nordg mount;
Diskgroup altered
SQL> alter diskgroup extdg mount;
Later I tried removing the the database configuration from the cluster using SRVCTL and added the database to cluster again.
srvctl remove instance -d dbrac -i dbrac1
srvctl remove instance -d dbrac -i dbrac2
srvctl remove database -d dbrac
srvctl add database -d dbrac -o /u01/app/oracle/product/11.2.0/dbhome_1 -a "extdg,nordg"
srvctl add instance -d dbrac -i dbrac2 -n vmsol2
srvctl add instance -d dbrac -i dbrac1 -n vmsol1
Still database is not starting during cluster startup.
Why did the disk group is not getting mounted while cluster is starting? Can someone help me?
Regards,
Mat
Edited by: user11278087 on Mar 9, 2012 7:37 PM
Edited by: user11278087 on Mar 9, 2012 7:41 PM
Edited by: user11278087 on Mar 9, 2012 7:42 PMHi,
Thank you for your replay.
Disk group was mounting previously without doing any modification in spfile after executing the following commands.
srvctl add database -d dbrac -o /u01/app/oracle/product/11.2.0/dbhome_1 -a "extdg,nordg"
srvctl add instance -d dbrac -i dbrac2 -n vmsol2
srvctl add instance -d dbrac -i dbrac1 -n vmsol1
But suddenly this issue happened.
I do not have metalink access. Could you please help me?
Regards,
Mat. -
Trying to create test project, and get NPE during server startup
Hi
I am trying to create simple test project using JSF RI (usually use myfaces), but I am getting a couple of NPE's during server startup.
I am using :
jetty (maven plugin)
jsf 1.2_03
facelets 1.1.12
I am probably missing something simple, but I just can't figure it out.
My web.xml:
<?xml version = '1.0' encoding = 'ISO-8859-1'?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
version="2.4">
<context-param>
<param-name>facelets.REFRESH_PERIOD</param-name>
<param-value>2</param-value>
</context-param>
<context-param>
<param-name>facelets.LIBRARIES</param-name>
<param-value>
/WEB-INF/tomahawk.taglib.xml
</param-value>
</context-param>
<context-param>
<param-name>facelets.DEVELOPMENT</param-name>
<param-value>true</param-value>
</context-param>
<context-param>
<param-name>javax.faces.STATE_SAVING_METHOD</param-name>
<param-value>client</param-value>
<!--param-value>server</param-value-->
</context-param>
<context-param>
<param-name>javax.faces.DEFAULT_SUFFIX</param-name>
<param-value>.xhtml</param-value>
</context-param>
<context-param>
<param-name>javax.faces.CONFIG_FILES</param-name>
<!-- /WEB-INF/faces-config.xml loaded by default -->
<param-value>
/WEB-INF/faces-config.xml,/WEB-INF/faces-beans.xml,/WEB-INF/faces-nav.xml
</param-value>
</context-param>
<!-- JSF 1.2 RI specifc -->
<!-- Listener implementation to handle web application lifecycle events -->
<listener>
<listener-class>
com.sun.faces.application.WebappLifecycleListener
</listener-class>
</listener>
<listener>
<listener-class>
com.sun.faces.config.ConfigureListener
</listener-class>
</listener>
<context-param>
<description>
Set this flag to true if you want the JavaServer Faces
Reference Implementation to validate the XML in your
faces-config.xml resources against the DTD. Default
value is false.
</description>
<param-name>com.sun.faces.validateXml</param-name>
<param-value>false</param-value>
</context-param>
<context-param>
<description>
Set this flag to true if you want the JavaServer Faces
Reference Implementation to verify that all of the application
objects you have configured (components, converters,
renderers, and validators) can be successfully created.
Default value is false.
</description>
<param-name>com.sun.faces.verifyObjects</param-name>
<param-value>true</param-value>
</context-param>
<!-- Faces Servlet -->
<servlet>
<servlet-name>faces</servlet-name>
<servlet-class>javax.faces.webapp.FacesServlet</servlet-class>
<load-on-startup>1</load-on-startup>
</servlet>
<!-- Faces Servlet Mappings -->
<servlet-mapping>
<servlet-name>faces</servlet-name>
<url-pattern>*.jsf</url-pattern>
</servlet-mapping>
<welcome-file-list>
<welcome-file>index.html</welcome-file>
</welcome-file-list>
</web-app>My faces-config.xml :
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE faces-config PUBLIC "-//Sun Microsystems, Inc.//DTD JavaServer Faces Config 1.1//EN"
"http://java.sun.com/dtd/web-facesconfig_1_1.dtd">
<faces-config>
<application>
<!-- view-handler>
org.rcfaces.core.internal.facelets.FaceletViewHandler
</view-handler-->
<view-handler>com.sun.facelets.FaceletViewHandler</view-handler>
<locale-config>
<default-locale>en</default-locale>
</locale-config>
</application>
</faces-config>My Stack traces :
INFO: Initializing Sun's JavaServer Faces implementation (1.2_03-b09-FCS) for context '/test'
2007-01-23 15:41:57.351::WARN: failed ContextHandler@964130{/test,file:/C:/code/tests/rcfacesTest/src/main/webapp/}
java.lang.NullPointerException
at com.sun.faces.application.ApplicationAssociate.getInstance(ApplicationAssociate.java:171)
at com.sun.faces.application.WebappLifecycleListener.handleAttributeEvent(WebappLifecycleListener.java:221)
at com.sun.faces.application.WebappLifecycleListener.attributeReplaced(WebappLifecycleListener.java:211)
at org.mortbay.jetty.handler.ContextHandler$Context.setAttribute(ContextHandler.java:1317)
at com.sun.faces.config.ConfigureListener$ApplicationMap.put(ConfigureListener.java:1885)
at com.sun.faces.renderkit.RenderKitUtils.loadSunJsfJs(RenderKitUtils.java:1076)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:468)
at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:450)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:124)
at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1136)
at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:420)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:120)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:119)
at org.mortbay.jetty.Server.doStart(Server.java:221)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
at org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:134)
at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:327)
at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:272)
at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:177)
at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:183)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
2007-01-23 15:41:57.367::WARN: failed ContextHandlerCollection@91b9b0
java.lang.NullPointerException
at com.sun.faces.application.ApplicationAssociate.getInstance(ApplicationAssociate.java:171)
at com.sun.faces.application.WebappLifecycleListener.handleAttributeEvent(WebappLifecycleListener.java:221)
at com.sun.faces.application.WebappLifecycleListener.attributeReplaced(WebappLifecycleListener.java:211)
at org.mortbay.jetty.handler.ContextHandler$Context.setAttribute(ContextHandler.java:1317)
at com.sun.faces.config.ConfigureListener$ApplicationMap.put(ConfigureListener.java:1885)
at com.sun.faces.renderkit.RenderKitUtils.loadSunJsfJs(RenderKitUtils.java:1076)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:468)
at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:450)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:124)
at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1136)
at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:420)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:120)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:119)
at org.mortbay.jetty.Server.doStart(Server.java:221)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
at org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:134)
at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:327)
at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:272)
at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:177)
at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:183)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
2007-01-23 15:41:57.367::WARN: failed HandlerCollection@1360c93
java.lang.NullPointerException
at com.sun.faces.application.ApplicationAssociate.getInstance(ApplicationAssociate.java:171)
at com.sun.faces.application.WebappLifecycleListener.handleAttributeEvent(WebappLifecycleListener.java:221)
at com.sun.faces.application.WebappLifecycleListener.attributeReplaced(WebappLifecycleListener.java:211)
at org.mortbay.jetty.handler.ContextHandler$Context.setAttribute(ContextHandler.java:1317)
at com.sun.faces.config.ConfigureListener$ApplicationMap.put(ConfigureListener.java:1885)
at com.sun.faces.renderkit.RenderKitUtils.loadSunJsfJs(RenderKitUtils.java:1076)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:468)
at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:450)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:124)
at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1136)
at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:420)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:120)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:119)
at org.mortbay.jetty.Server.doStart(Server.java:221)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
at org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:134)
at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:327)
at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:272)
at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:177)
at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:183)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
2007-01-23 15:41:57.523::INFO: Started SelectChannelConnector @ 0.0.0.0:8080
2007-01-23 15:41:57.523::WARN: failed Server@188f506
java.lang.NullPointerException
at com.sun.faces.application.ApplicationAssociate.getInstance(ApplicationAssociate.java:171)
at com.sun.faces.application.WebappLifecycleListener.handleAttributeEvent(WebappLifecycleListener.java:221)
at com.sun.faces.application.WebappLifecycleListener.attributeReplaced(WebappLifecycleListener.java:211)
at org.mortbay.jetty.handler.ContextHandler$Context.setAttribute(ContextHandler.java:1317)
at com.sun.faces.config.ConfigureListener$ApplicationMap.put(ConfigureListener.java:1885)
at com.sun.faces.renderkit.RenderKitUtils.loadSunJsfJs(RenderKitUtils.java:1076)
at com.sun.faces.config.ConfigureListener.contextInitialized(ConfigureListener.java:468)
at org.mortbay.jetty.handler.ContextHandler.startContext(ContextHandler.java:450)
at org.mortbay.jetty.servlet.Context.startContext(Context.java:124)
at org.mortbay.jetty.webapp.WebAppContext.startContext(WebAppContext.java:1136)
at org.mortbay.jetty.handler.ContextHandler.doStart(ContextHandler.java:420)
at org.mortbay.jetty.webapp.WebAppContext.doStart(WebAppContext.java:467)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
at org.mortbay.jetty.handler.ContextHandlerCollection.doStart(ContextHandlerCollection.java:120)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
at org.mortbay.jetty.handler.HandlerCollection.doStart(HandlerCollection.java:156)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
at org.mortbay.jetty.handler.HandlerWrapper.doStart(HandlerWrapper.java:119)
at org.mortbay.jetty.Server.doStart(Server.java:221)
at org.mortbay.component.AbstractLifeCycle.start(AbstractLifeCycle.java:39)
at org.mortbay.jetty.plugin.Jetty6PluginServer.start(Jetty6PluginServer.java:134)
at org.mortbay.jetty.plugin.AbstractJettyMojo.startJetty(AbstractJettyMojo.java:327)
at org.mortbay.jetty.plugin.AbstractJettyMojo.execute(AbstractJettyMojo.java:272)
at org.mortbay.jetty.plugin.AbstractJettyRunMojo.execute(AbstractJettyRunMojo.java:177)
at org.mortbay.jetty.plugin.Jetty6RunMojo.execute(Jetty6RunMojo.java:183)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:488)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:458)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO] Jetty server exiting.Thanks,
MikeThis has been fixed in the RI head. Hopefully we'll be able to get a 1.2_04 out shortly.
Please download a nightly from the RI project site and give that a shot. -
My iphone 3GS keeps freezing and showing the apple logo during phone calls. Can anybody help plese ? Bja
Hiya thankyou for the answer.
Trying to set it up as a new device but can't find the backup to save it.
I have no "mediasync" folder in my library/application support. Did these folders get moved around with Lion?
Thankyou again,
Maybe you are looking for
-
Email address mix up in my mail
My email address has taken on the name Canada Copeland when my name is Donna Copeland. I have checked my accounts preference and that has my correct name but when I go to send a message my email address comes up as Canada Copeland. My service provid
-
How to maintain experience requirement for a position
Hi All, There is a very common requirement for a position like "5 years of experience in management level" I dont know how to maintain this requirement in SAP. right now we have created a qualification named "Management Experience" with a time scale
-
Hi Guys , I have a work flow requirement , In Which i have to know in Purchase requisition items history . how to identify the new item and change items for triggering the work flow . Here i am using a badi to triger an event . ( BADI : ME_REQ_POSTE
-
when i run after effects i keep getting this, the procedure entry point amtretrievelibrarypath could noy be located in the dynamic link library amtlib.dll. I've treid to getanother amtlib.dll from photoshop but it doesnt work any help?
-
Since a while, we are using RMS 3.00 (e-Recruiting) for job applications. The configuration exists of one, standalone server on which employees from inside the company have access (via iViews on SAP Portal) and also the "outside" world but via the st