When creating index using Oracle Text, it gave the followings:
ERROR [com.n.oss.server.scontainer.persistence.schemagen.PersistenceSchemaManager] Error in amendAfter class com.n.secureaccess.server.migration.all_versions.SecureAccessAmender
SQL problem: java.sql.SQLException: ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-20000: Oracle Text error:
DRG-10758: index owner does not have the privilege to use file or URL datastore
ORA-06512: at "CTXSYS.DRUE", line 186
ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 320
Solution:
Note, beginning 18.1, instead of setting the FILE_ACCESS_ROLE no longer exists. Instead grant TEXT DATASTORE ACCESS role to the user that needs to use FILE or URL datastore:
If you are installing Weblogic in remote server, direct java installation will not go to console mode after it fails Display check. After version 12.2.1.2.0 -mode=console option was taken out ("stupid decision").
I assume you already completed the followings:
1. Install JDK 8 (let's say JAVA_HOME is under /opt/app/java/jdk)
2. Download fmw_12.2.1.4.0_wls.jar from oracle.com
3. Copy the file into /opt/app/install/12c
Now, you need to do as followings:
1) Create Home directory:
mkdir /opt/app/12c/middleware
2) Create response file:
cd /opt/app/install/12c
vi myrsp.rsp
ORACLE_HOME=/opt/app/12c/middleware
#Set this variable value to the Installation Type selected. e.g. WebLogic Server, Coherence, Complete with Examples.
INSTALL_TYPE=WebLogic Server
#Provide the My Oracle Support Username. If you wish to ignore Oracle Configuration Manager configuration provide empty string for user name.
MYORACLESUPPORT_USERNAME=
#Provide the My Oracle Support Password
MYORACLESUPPORT_PASSWORD=<SECURE VALUE>
#Set this to true if you wish to decline the security updates. Setting this to true and providing empty string for My Oracle Support username will ignore the Oracle Configuration Manager configuration
DECLINE_SECURITY_UPDATES=true
#Set this to true if My Oracle Support Password is specified
SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
It should show you "The installation of Oracle ...... 12.2.1.4.0 completed successfully."
ADF
Now, if you want to install ADF (Application Runtime) 12c, you can do followings:
1) Download fmw_12.2.1.4.0_infrastructure.jar
2) Prepare response file:
cd /opt/app/install/12c
cp myrsp.rsp adf.rsp
vi adf.rsp
[ENGINE]
Response File Version=1.0.0.0.0
[GENERIC]
#types: SOFTWARE ONLY TYPE,BASIC TYPE and ADVANCED TYPE. ADVANCED TYPE=true
INSTALL_TYPE=Fusion Middleware Infrastructure
ORACLE_HOME=/opt/app/12c/middleware
MW_HOME=/opt/app/12c/middleware
#Provide the My Oracle Support Username. If you wish to ignore Oracle Configuration Manager configuration provide empty string for user name.
MYORACLESUPPORT_USERNAME=
#Provide the My Oracle Support Password
MYORACLESUPPORT_PASSWORD=<SECURE VALUE>
#Set this to true if you wish to decline the security updates. Setting this to true and providing empty string for My Oracle Support username will ignore the Oracle Configuration Manager configuration
DECLINE_SECURITY_UPDATES=true
#Set this to true if My Oracle Support Password is specified
SECURITY_UPDATES_VIA_MYORACLESUPPORT=false
1.Create VM with 3 NetCard (1. NAT:dhcp – for
external use, 2. Host-only: Static – for internal use, 3. Bridge Net: Static –
for local intranet).
Example of network configuration
(/etc/network/interfaces):
auto lo
iface lo inet loopback
# The primary network interface
auto enp0s3
iface enp0s3 inet dhcp
#Virbr
auto virbr0
iface virbr0 inet dhcp
#Host-only Net for local VM use
auto enp0s8
iface enp0s8 inet static
address 192.168.56.204
netmask 255.255.255.0
network 192.168.56.0
#Bridge Net for local network use
auto enp0s9
iface enp0s9 inet static
address 192.168.1.24
netmask 255.255.255.0
If you clone from existing VM, change
hostname file (/etc/hostname) and hosts file accordingly. Configure your VMs
with 2Gb of RAM for normal work. In my case, I used 1.5Gb and still ok.
2.You should be a root user to install all. You
should not have a group called docker. If it is change it using: groupmod –n
.
3.Disable swap on your disk (kubeadm won’t work
with swap on):
swapoff –a
(better to comment
out swap line on fstab. Be careful don’t comment disk or boot volumes or yr
system won’t start)
vi /etc/fstab
4.Update your OS packages: sudo apt-get update
5.Install standard docker: apt-get install –qy docker.io
9.We can use Flannel (https://github.com/coreos/flannel)
for Software Defined Network SDN using overlay and ipvlan of Linux kernel. This
automated network for our PODs and nodes’ heartbeat communication.
10.Find out network interfaces and IPs: ifconfig
In my case: enp0s3 is dhcp for external on
10.0.2.0 subnet and enp0s8 for internal on 192.168.56.0 subnet. We need to use
internal IP address for Kubernetes API transfers:
Set /proc/sys/net/bridge/bridge-nf-call-iptablesto 1 by running sysctl
net.bridge.bridge-nf-call-iptables=1 to pass bridged IPv4 traffic to iptables’ chains.
This is a requirement for some CNI plugins to work, for more information please
see here.
I use Flannel here (https://github.com/coreos/flannel):
19.Check running components of Kubernetes
(everything should be running on Status):
kubectl get all --namespace=kube-system
20.Let’s try to deploy a pod with container and
check it out:
kubectl run mynginx --image=nginx --port=80
21.Check if it is deployed:
kubectl get pods
kubectl get deploy
22.Check it out in details (kubectl describe pod
, kubectl logs
):
kubectl describe po mynginx
kubectl logs mynginx-6cd7b4779c-gbxww
23.You can login into container using kubectl exec:
$ kubectl exec -it mynginx-6cd7b4779c-gbxww sh
# head -n3 /etc/os-release
PRETTY_NAME="Debian GNU/Linux 9 (stretch)"
NAME="Debian GNU/Linux"
VERSION_ID="9"
# exit
24.You can expose it to external IP for you to be
able to see from external browser (in our case, laptop where VirtualBox
installed). I put my Node2 IP address as I don’t have external LoadBalancer. I
see container is in there by kubectl get pods –output=wide:
kubectl expose pod mynginx-6cd7b4779c-2nvnt --type=NodePort
–name myninx-servc
25.Now, we can open a browser from our laptop as http://192.168.1.42/ or if you exposed with
NodePort type, check for exposed port by kubectl get svc and use that with IP
address.
26.For cleanup:
kubectl delete services my-service
kubectl delete deployment mynginx
27.If you want to use WebUI tool to see everything
on the dashboard (https://kubernetes.io/docs/tasks/access-application-cluster/web-ui-dashboard/)
- Downloaded OpenThinClient for VM and configured in VirtualBox.
- Logged in to OpenThinClient Debian and opened ThinClient manager.
- Created VM without HDD and made bootable from NetCard. Then started up.
- After DHCP IP retrieval, I added PXE client from OpenThinClient Manager.
- When I rebooted client VM,
I got this error: Nothing to boot: No such file or directory (http://ipxe.org/2d03e13b) No more network devices FATAL: Could not read from the boot medium! System halted.
They said it is a known bug for VirtualBox and solution would be: Change the Network >> Adapter Type from “Intel PRO/1000 MT Desktop” to “PCnet-FAST III” from VM Settings.
But, this didn't work for me.
I rebooted VM client and pressed Ctrl+B when prompted to do so. dhcp
then chained it manually chain tftp://192.168.1.15/pxelinux.0
