When You install oem12c release 3 as upgrade on previous version and update all agents on remote hosts to actual version, there are one more step to end entire process – remove old binaries of previous agent. This will be done later, so don’t hurry with this operation. Be sure first that new one agent is working correctly.
OMS in unavailable – Backend WLS or EM application seems to be down
When i tried to run again my test machine (vmware), started up database and OMS, and i tried to launch oms console to log into it i spotted new error:
Fedora installation are starting with strange interface name.
Interface name have strange name – “eno…“, “p4p1“, “eno33“… or something like that?
How to set it to “normal” eth0 name?
When i tried to configure my newly created virtual machine, when i tried to ssh to her, my connection are dropped.
But why?…
When i upgraded my VMware9 machine to VMware10, i lost network.
Card was renamed to strange name…
Polish
Afrikaans
Albanian
Amharic
Arabic
Armenian
Azerbaijani
Basque
Belarusian
Bengali
Bosnian
Bulgarian
Catalan
Cebuano
Chichewa
Chinese (Simplified)
Chinese (Traditional)
Corsican
Croatian
Czech
Danish
Dutch
English
Esperanto
Estonian
Filipino
Finnish
French
Frisian
Galician
Georgian
German
Greek
Gujarati
Haitian Creole
Hausa
Hawaiian
Hebrew
Hindi
Hmong
Hungarian
Icelandic
Igbo
Indonesian
Irish
Italian
Japanese
Javanese
Kannada
Kazakh
Khmer
Korean
Kurdish (Kurmanji)
Kyrgyz
Lao
Latin
Latvian
Lithuanian
Luxembourgish
Macedonian
Malagasy
Malay
Malayalam
Maltese
Maori
Marathi
Mongolian
Myanmar (Burmese)
Nepali
Norwegian
Pashto
Persian
Portuguese
Punjabi
Romanian
Russian
Samoan
Scottish Gaelic
Serbian
Sesotho
Shona
Sindhi
Sinhala
Slovak
Slovenian
Somali
Spanish
Sudanese
Swahili
Swedish
Tajik
Tamil
Telugu
Thai
Turkish
Ukrainian
Urdu
Uzbek
Vietnamese
Welsh
Xhosa
Yiddish
Yoruba
Zulu